Publish Release (moi-computer)
npm release runbook: local verify, tag push, gated CI publish, then restore
Test report
- Verdict
- Works with setup
- Score
- Tested
- Jul 29, 2026
- Environment
- Claude Code 2.x (agent harness)
- Upstream re-checked
- Jul 30, 2026 · 9eea1d9
⚠ This skill is no longer available upstream. Our re-check on Aug 10, 2026 couldn't find it any more (repo unreachable/deleted). The test below is what we measured on Jul 29, 2026 and we're leaving it up as a record — but there is nothing left to install, so we've removed the command.
Queued here as publish-next; git history shows upstream deleted that path and the replacement, publish-release, now covers both next previews and stable releases. Ran its read-only phases live against a fresh clone: lint and format check clean, 708 tests pass, and bun pm pack produced a tarball with 70 dist/ entries and zero hits on its secrets scan. Its version rule earns its keep right now, because npm shows next at 0.4.1-next.0 while latest is 0.5.1, so both obvious no-skill answers sort below stable and would publish a preview containing older code than the release; the rule in the skill yields 0.5.2-next.0, which sorts above. I also reproduced the tar bug it documents: with two moi-computer-*.tgz files in the tree the unpinned glob makes tar treat the rest as members, and the dist/ count comes back 0 against a perfectly good tarball. The catch is scope - the package name, repo, release workflow and the hardcoded port 13059 are all baked in, so outside molefrog/moi this is something you rewrite, not something you run.
Scored on four weighted criteria — install, triggering, output vs. baseline, docs. How scoring works
- Installs cleanly 5/5
- Triggers reliably 5/5
- Output vs. baseline 8/10
- Docs & honesty 5/5
What Publish Release (moi-computer) does
A step-by-step release runbook for the moi-computer npm package: preflight on a clean main, a local verify pass that mirrors CI, version selection for next previews or stable, tag push into a reviewer-gated GitHub Actions publish, post-publish verification of dist-tags and provenance, and a restore phase that puts the dev link back. Triggers on requests to publish, release, ship a version, or cut a dev preview inside that repo. Every command is hardcoded to that package and workflow, so elsewhere it reads as a template rather than a runnable skill.
How to install Publish Release (moi-computer)
Nothing to install: the source repository no longer has this skill. If the author brings it back, our daily re-check will pick it up and the command will reappear here.
Commands — how to trigger Publish Release (moi-computer)
-
/publish-releasenpm release runbook: local verify, tag push, gated CI publish, then restore
It also activates on plain-language prompts like these:
-
Cut a next preview release of moi-computer from main -
Is this repo in a publishable state, and what version should ship next? -
Ship v0.5.2 of moi-computer through the gated CI publish workflow
Frequently asked questions
- Is the Publish Release (moi-computer) skill free?
- Yes. The skill itself is free from molefrog/moi. SkillProof publishes the install command and an independent test verdict at no cost.
- Does Publish Release (moi-computer) work with Claude Code?
- We tested it with Claude Code 2.x (agent harness) on Jul 29, 2026. Verdict: Works with setup. Queued here as publish-next; git history shows upstream deleted that path and the replacement, publish-release, now covers both next previews and stable releases. Ran its read-only phases live against a fresh clone: lint and format check clean, 708 tests pass, and bun pm pack produced a tarball with 70 dist/ entries and zero hits on its secrets scan. Its version rule earns its keep right now, because npm shows next at 0.4.1-next.0 while latest is 0.5.1, so both obvious no-skill answers sort below stable and would publish a preview containing older code than the release; the rule in the skill yields 0.5.2-next.0, which sorts above. I also reproduced the tar bug it documents: with two moi-computer-*.tgz files in the tree the unpinned glob makes tar treat the rest as members, and the dist/ count comes back 0 against a perfectly good tarball. The catch is scope - the package name, repo, release workflow and the hardcoded port 13059 are all baked in, so outside molefrog/moi this is something you rewrite, not something you run.
- What is the Publish Release (moi-computer) SkillProof Score?
- 9.2/10 — installs cleanly 5/5, triggers reliably 5/5, output vs. baseline 8/10, docs & honesty 5/5.
- How do I install Publish Release (moi-computer)?
- Copy the install command from this page, run it in your terminal, and restart Claude Code. Skills live in ~/.claude/skills/ (global) or .claude/skills/ inside a project.
- Can I use Publish Release (moi-computer) with Cursor, Copilot, Gemini CLI, Codex or other AI tools?
- The SKILL.md format is native to Claude (Claude Code, Desktop, claude.ai). The instructions inside adapt to other assistants: Cursor rules, GitHub Copilot instructions, Windsurf rules, Custom GPTs, AGENTS.md for OpenAI Codex, and GEMINI.md for Google Gemini CLI — our conversion guides cover each, and the free converter on the tools page does the wrapping for you.