Agent skill
Nethercore ZX Publishing Workflow
This skill covers publishing ZX games. Use when the user asks to "publish game", "release game", "upload game", "create ROM", "package game", "nether pack", or mentions ROM packaging, nethercore.systems upload. **Load references when:** - Full manifest examples → `references/manifest-examples.md`
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/publishing-workflow-nethercore-systems-nethercore-ai-plugin
SKILL.md
Nethercore ZX Publishing Workflow
nether CLI Commands
| Command | Purpose |
|---|---|
nether init |
Create nether.toml manifest |
nether compile |
Compile WASM from source |
nether pack |
Bundle WASM + assets into ROM |
nether build |
compile + pack (main command) |
nether run |
Build and launch in emulator |
Game Manifest (nether.toml)
[game]
id = "my-game" # Unique identifier
title = "My Game" # Display name
author = "Your Name" # Creator
version = "1.0.0" # Semantic version
description = "A fun game" # Short description
tags = ["arcade", "2d"] # Searchable tags
[build]
script = "cargo build --target wasm32-unknown-unknown --release"
wasm = "target/wasm32-unknown-unknown/release/my_game.wasm"
[[assets.textures]]
id = "player"
path = "assets/player.png"
Upload to nethercore.systems
Required:
| File | Format |
|---|---|
| Game | .wasm or .nczx |
| Icon | 64x64 PNG |
Optional:
- Screenshots (PNG, up to 5)
- Banner (1280x720 PNG)
Process:
- Create account at nethercore.systems
- Dashboard → "Upload New Game"
- Fill metadata, upload files
- Publish
Pre-Release Checklist
-
nether buildsucceeds -
nether run --sync-testpasses (if multiplayer) - ROM under 16MB
- Icon is 64x64 PNG
- Description is compelling
Versioning
Semantic versioning: major.minor.patch
Update process:
- Bump version in nether.toml
- Rebuild
- Re-upload to platform
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
majiayu000/claude-skill-registry
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
majiayu000/claude-skill-registry
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
majiayu000/claude-skill-registry
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
majiayu000/claude-skill-registry
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
majiayu000/claude-skill-registry
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
majiayu000/claude-skill-registry
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?