npm Package Publisher
klaudworks/universal-skills
Releases an npm package by committing changes, bumping the version with npm version, pushing the tag and checking the GitHub Actions publish.
Cut a Mission Control desktop release — bump package.json (must match the git tag), commit, create an annotated v-tag, push to trigger release.yml CI.
Install Release
$ npx skills add AgentSystemLabs/mission-control --skill release -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install AgentSystemLabs/mission-control release --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/AgentSystemLabs/mission-control.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/release .claude/skills/release && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "release" agent skill from https://github.com/AgentSystemLabs/mission-control/tree/main/.agents/skills/release into .claude/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/AgentSystemLabs/mission-control/tree/main/.agents/skills/releaseType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add AgentSystemLabs/mission-control --skill release -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install AgentSystemLabs/mission-control release --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AgentSystemLabs/mission-control.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/release .agents/skills/release && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "release" agent skill from https://github.com/AgentSystemLabs/mission-control/tree/main/.agents/skills/release into .agents/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add AgentSystemLabs/mission-control --skill release -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install AgentSystemLabs/mission-control release --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AgentSystemLabs/mission-control.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/release .cursor/skills/release && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "release" agent skill from https://github.com/AgentSystemLabs/mission-control/tree/main/.agents/skills/release into .cursor/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/AgentSystemLabs/mission-control.git --path .agents/skills/release--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add AgentSystemLabs/mission-control --skill release -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install AgentSystemLabs/mission-control release --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AgentSystemLabs/mission-control.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/release .gemini/skills/release && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "release" agent skill from https://github.com/AgentSystemLabs/mission-control/tree/main/.agents/skills/release into .gemini/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install AgentSystemLabs/mission-control releaseInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add AgentSystemLabs/mission-control --skill release -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/AgentSystemLabs/mission-control.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/release .github/skills/release && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "release" agent skill from https://github.com/AgentSystemLabs/mission-control/tree/main/.agents/skills/release into .github/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add AgentSystemLabs/mission-control --skill release -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install AgentSystemLabs/mission-control release --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AgentSystemLabs/mission-control.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/release .opencode/skills/release && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "release" agent skill from https://github.com/AgentSystemLabs/mission-control/tree/main/.agents/skills/release into .opencode/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
release- GitHub stars
- 159
- Token cost
- ~1.3k tokens
- SKILL.md length
- 530 words
- Files
- 2 (incl. references)
- Skills in repo
- 3
- Repo updated
- First seen
- Licence
- MIT
At a glance
Cut a Mission Control desktop release — bump package.json (must match the git tag), commit, create an annotated v-tag, push to trigger release.yml CI.
- Works in 6 steps: Preflight → 5 — Quality gate → Compute next version → …
- Automation was skipped with [skip release]
- SKILL.md covers Mission Control rules…, Phase 1 — Preflight, Phase 1.5 — Quality gate and Phase 2 — Compute next version, plus 4 more sections
- Calls git, pnpm and node
What it does
Release is an agent skill from AgentSystemLabs/mission-control. Cut a Mission Control desktop release — bump package.json (must match the git tag), commit, create an annotated v-tag, push to trigger release.yml CI. Prefer letting auto-tag-release.yml patch-bump on merges to main; use this skill for major/minor, hotfixes, or when automation was skipped with [skip release]. Read references/mission-control-release.md for the full CI pipeline, academy approval gate, and version alignment rules.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/mission-control-release.md`).
It sits in Development, covering CI/CD. It works with npm, Git and GitHub. The licence is MIT.
When your agent uses it
- Automation was skipped with [skip release]
- Tasks that involve CI/CD
Example prompts
- “/release”
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 92b91d0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
gitpnpmnode
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git and pnpm, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Release loads about 1.3k tokens when it runs, and up to ~3.2k if it reads all its reference files. Until then it costs about 110 tokens; SKILL.md has 530 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from AgentSystemLabs/mission-control at commit 92b91d0, republished under its MIT licence (© AgentSystemLabs). 530 words, ~1,318 tokens.
Download SKILL.mdSave it as
.claude/skills/release/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- release
- description
- Cut a Mission Control desktop release — bump package.json (must match the git tag), commit, create an annotated v-tag, push to trigger release.yml CI. Prefer letting auto-tag-release.yml patch-bump on merges to main; use this skill for major/minor, hotfixes, or when automation was skipped with [skip release]. Read references/mission-control-release.md for the full CI pipeline, academy approval gate, and version alignment rules.
Mission Control release
Phased workflow for this Electron desktop app. Read references/mission-control-release.md for CI jobs, academy publishing, auto-tag automation, and the v0.47.1 version-mismatch incident.
Default path: merges to main are automatically patch-bumped and tagged by .github/workflows/auto-tag-release.yml after Hosted CI is green. Prefer that unless the user asked for a major/minor bump or a manual hotfix.
Bump type from args: major | minor | patch. Default patch for this repo (desktop app ships frequently).
Quality mode: mode=fast|balanced|production. Default production when cutting a public release.
Mission Control rules (non-negotiable)
- Bump
package.jsonbefore creating the git tag. The tag version (withoutv) andpackage.jsonversionmust be identical on the commit you tag. - Use
pnpm version X.Y.Z --no-git-tag-version— nevergit tagfirst and bump later. - Never reuse or force-move a remote tag. If a bad tag shipped, bump to the next patch and release again.
- Pushing the tag triggers
release.yml— CI builds signed installers, uploads academy assets, finalizes the academy row (Approve unlocks), and attaches installers to the GitHub Release. It does not Approve / promote the Electron updater. - In-app Update / electron-updater only advance after you Approve on agentsystem.dev. GitHub Releases are for manual download only. Admin Waiting means not finalized yet (CI finalize failed or still running).
- Verify after CI + after academy approval: GitHub assets + finalized draft exist after CI; academy public
latestVersiononly matches after you Approve.
Version alignment check (run before tagging)
PKG=$(node -p "require('./package.json').version")
echo "package.json: $PKG — tag will be v$PKG"
git rev-parse "v$PKG" 2>/dev/null && echo "ERROR: tag v$PKG already exists" && exit 1Phase 1 — Preflight
Exit condition: clean tree on main, last tag known.
git status --porcelain
git rev-parse --abbrev-ref HEAD
git describe --tags --abbrev=0 2>/dev/null || echo "NO_PRIOR_TAG"
git remote -v
node -p "require('./package.json').version"- Dirty tree → STOP.
- Not on
main→ confirm with user. - Manifest:
package.jsononly (notpublish/package.json). - If the next merge would auto-tag and the user only wanted a delay → suggest
[skip release]on the merge commit instead.
Phase 1.5 — Quality gate
Release range: <last-tag>..HEAD (or full history if no tag).
mode=production→ run typecheck + lint + tests (pnpm typecheck,pnpm lint,pnpm test) on changed scope.mode=fast→ residue sweep on release-range diff.
Stop on failure unless user explicitly bypasses (record Bypassed-gates: in tag body).
Show full SKILL.md (203 more words)Show less
Phase 2 — Compute next version
From current package.json version, apply semver bump. Verify tag does not exist:
git rev-parse v$NEXT_VERSION 2>/dev/null && echo "TAG_EXISTS — pick next patch or delete stale tag deliberately"Phase 3 — Write manifest
pnpm version $NEXT_VERSION --no-git-tag-versionShow diff. Only package.json should change (no lockfile version field in pnpm for the root package).
Phase 4 — Release notes
Range: LAST_TAG..HEAD (exclude the upcoming chore(release) commit if notes are generated before bump).
Use conventional-commit grouping when ≥50% of subjects match feat: / fix: / chore: etc.
Example annotation:
## v0.48.0 (2026-07-02)
### Features
- feat: add foo (abc1234)
### Fixes
- fix: bar (def5678)Phase 5 — Commit, tag, push
git add package.json
git commit -m "chore(release): v$NEXT_VERSION"
git tag -a "v$NEXT_VERSION" -m "<release notes>"
git push --follow-tagsWhen the user explicitly requests push in the same turn, push immediately after local tag creation.
Monitor: GitHub Actions → Release workflow for the new tag. Wait for finalize-academy and publish-github to succeed. Remind the user that existing users are not prompted until they Approve the release on agentsystem.dev (Waiting/Draft means finalize has not completed).
NEVER
- NEVER tag before bumping
package.json— causes permanent in-app update loops (see v0.47.1). - NEVER push a tag whose commit still has the old
package.jsonversion. - NEVER force-push or delete a published tag without explicit user request and understanding of academy/CI impact.
- NEVER use lightweight tags — always
git tag -a. - NEVER release from a dirty working tree.
- NEVER tell the user the updater is live just because GitHub Release assets exist — academy approval is the updater gate.
© AgentSystemLabs, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (references) in .agents/skills/release of AgentSystemLabs/mission-control.
- SKILL.md
- references/mission-control-release.md
Open the folder on GitHubat commit 92b91d0
Compare with similar skills
Release next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Release this skillAgentSystemLabs/mission-control | 159 | — | ~1.3k | Automated safety check: Pass | MIT | |
| npm Package Publisherklaudworks/universal-skills | 181 | — | ~923 | Automated safety check: Pass | MIT | |
| ClickUp CLI Release Processkrodak/clickup-cli | 120 | — | ~906 | Automated safety check: Warn | MIT | |
| CI Triageandymai/brepjs | 114 | — | ~3.7k | Automated safety check: Pass | Apache-2.0 | |
| Hunk Release Workflowmodem-dev/hunk | 9.5k | — | ~3.8k | Automated safety check: Pass | MIT | |
| Worktrunk Release Workflowmax-sixty/worktrunk | 8.9k | — | ~6.9k | Automated safety check: Pass | Custom licence |
Similar skills
ClickUp CLI Release Process
krodak/clickup-cli
Walks through releasing a new version of clickup-cli: pre-release checks, version bump, tagging, CI watch, release notes and the Homebrew update.
CI Triage
andymai/brepjs
This skill should be used when a brepjs GitHub Actions job is red or behaving oddly on github.com (a remote CI run, not a local pre-commit/pre-push hook) — "CI failed", "ci-pass is failing", "npm ci…
Hunk Release Workflow
modem-dev/hunk
Maintainer workflow for preparing, publishing, verifying and curating Hunk releases, with confirmation gates before tags, publishes and public edits.
Worktrunk Release Workflow
max-sixty/worktrunk
Walks a maintainer through cutting a Worktrunk release: sync the release branch, pass two test gates, review the changes, then publish.
Coffee GB Release
trekawek/coffee-gb
Releases the current Coffee GB Maven snapshot through the GitHub Maven release workflow, then verifies and curates the tag and GitHub release.
More from AgentSystemLabs/mission-control
Diagram
AgentSystemLabs/mission-control
Show Mermaid diagrams in Mission Control's diagram viewer instead of dumping raw syntax in the terminal.
Recall
AgentSystemLabs/mission-control
Save durable project knowledge to Mission Control's Recall (project memory) so future sessions start already knowing it, AND navigate this project's indexed code graph.
Related
Categories
Questions about Release
What does Release do?
Cut a Mission Control desktop release — bump package.json (must match the git tag), commit, create an annotated v-tag, push to trigger release.yml CI. Release is an agent skill from AgentSystemLabs/mission-control.yml CI.
When should I use Release?
Release fits situations like: automation was skipped with [skip release]; tasks that involve CI/CD.
How do I install Release in Claude Code?
Run `npx skills add AgentSystemLabs/mission-control --skill release -a claude-code`. Or copy the skill folder (.agents/skills/release in AgentSystemLabs/mission-control) into .claude/skills/release in your project. Claude Code loads it when a task matches its description.
How do I install Release in Codex?
Run `npx skills add AgentSystemLabs/mission-control --skill release -a codex`. Or copy the skill folder (.agents/skills/release in AgentSystemLabs/mission-control) into .agents/skills/release in your project. Codex loads it when a task matches its description.
Can I use Release in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add AgentSystemLabs/mission-control --skill release -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/release, .gemini/skills/release, .github/skills/release and .opencode/skills/release in your project.
What does Release need to run?
Going by SKILL.md and its folder, Release needs the command-line tools its instructions call (git, pnpm and node).
Does Release access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Release safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Release use?
Release is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Release use?
About 1.3k tokens (SKILL.md is roughly 5.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.9k tokens, read only when the agent opens those files.
What are the alternatives to Release?
Skills that share tags, products or a category with Release: npm Package Publisher (klaudworks/universal-skills, 181 stars), ClickUp CLI Release Process (krodak/clickup-cli, 120 stars), CI Triage (andymai/brepjs, 114 stars) and Hunk Release Workflow (modem-dev/hunk, 9.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Release?
AgentSystemLabs (a GitHub organization) maintains it in AgentSystemLabs/mission-control, which has 159 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on September 22, 2026.
Source: AgentSystemLabs/mission-control on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.