How do I install the Publishing skill?

Run npx skillmds@latest add nethercore-systems/publishing in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Publishing safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Publishing?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Publishing free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under Apache-2.

Who published Publishing?

nethercore-systems (@nethercore-systems) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Publishing by nethercore-systems — Agent Skill

Name: Publishing
Rating: 4.5 (4 reviews)
Author: nethercore-systems

Publishing

Publishing Nethercore games to nethercore.systems. Covers ROM packaging with nether pack, release builds, platform upload requirements, versioning, and CI/CD pipeline setup with GitHub Actions. Use when preparing a game for release or setting up automated builds.

File contents

Nethercore Publishing

Prepare a verified release artifact; publishing/upload is a separate externally visible action requiring user authorization.

nether build              # release by default: compile + pack
nether run --no-build     # verify the resulting cart

Use nether build --debug only for a diagnostic build, not --release (unsupported). nether pack does not compile: use it after a deliberate external WASM/asset preparation step.

Release checks

Explicit manifest version, build output, player count, tick rate and netplay intent.
Actual console ROM/RAM/VRAM budgets and required resources verified; ZX ROM ceiling is 16 MiB.
Native rule tests, real input/render/audio path, and relevant rollback checks against the exact final cart.
Metadata/screenshots and asset rights checked. Read the current platform upload UI/backend contract before asserting icon/banner dimensions, accepted file types or screenshot counts; old prompt-pack values are not release requirements.
Preserve required debugging/provenance information, not build caches. A successful build is not proof an upload was published.

Version in [game].version; update the project's existing changelog/tag workflow as requested. Do not auto-tag, release or upload merely because a game was built.

See ROM packaging and CI workflow guidance.

Frequently asked questions