Release All
paperboytm/spool
Publish the complete Spool CLI release train: synchronized versions, npm packages, the GitHub release, and the matching production web deployment.
Use ONLY when the user explicitly asks to cut/publish a Huabu desktop release or tag a version.
$ npx skills add microsoft/Huabu --skill release -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install microsoft/Huabu 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/microsoft/Huabu.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/microsoft/Huabu/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/microsoft/Huabu/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 microsoft/Huabu --skill release -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install microsoft/Huabu release --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/microsoft/Huabu.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/microsoft/Huabu/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 microsoft/Huabu --skill release -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install microsoft/Huabu release --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/microsoft/Huabu.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/microsoft/Huabu/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/microsoft/Huabu.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 microsoft/Huabu --skill release -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install microsoft/Huabu release --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/microsoft/Huabu.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/microsoft/Huabu/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 microsoft/Huabu 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 microsoft/Huabu --skill release -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/microsoft/Huabu.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/microsoft/Huabu/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 microsoft/Huabu --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 microsoft/Huabu release --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/microsoft/Huabu.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/microsoft/Huabu/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.
releaseUse ONLY when the user explicitly asks to cut/publish a Huabu desktop release or tag a version.
Release is an agent skill from microsoft/Huabu, published by the product's own GitHub organization. Use ONLY when the user explicitly asks to cut/publish a Huabu desktop release or tag a version. Performs an outward action — bumps the version in apps/desktop/package.json, commits + annotated-tags vX.Y.Z, and pushes the branch + tag. That tag push auto-builds the macOS/Windows installers and publishes a GitHub Release. Provides status, bump, tag-push, and a one-command run (bump → tag-push).
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including scripts (for example `scripts/release.sh`).
It sits in DevOps & Cloud. It works with GitHub, npm, macOS and GitHub Actions. The repository describes itself as: Huabu, where you and your agents think together. The licence is MIT.
Read from SKILL.md and the folder at commit dc0cfa9. It shows what the files ask for, not the result of running them.
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.
Ships 1 file in scripts/ (Shell), which the agent can run.
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Release loads about 1.1k tokens when it runs. Until then it costs about 103 tokens; SKILL.md has 450 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.
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); the scripts in this folder are not scanned.
The full file from microsoft/Huabu at commit dc0cfa9, republished under its MIT licence (© microsoft). 450 words, ~1,084 tokens.
.claude/skills/release/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.Huabu ships exactly one artifact: the Huabu desktop (Electron) app. So there is one version per release, held in apps/desktop/package.json. A release bumps that version, makes one Release vX.Y.Z commit + annotated tag, and pushes the branch + tag.
Everything past the push is automatic and lives in GitHub Actions: pushing a vX.Y.Z tag fires .github/workflows/release.yml, which builds the macOS + Windows installers and publishes them as a GitHub Release (with auto-generated notes) attached to that tag. The skill does not await that build — follow it in the Actions tab (workflow "Release").
The whole release is therefore just run = bump → tag-push.
.agents/skills/release/scripts/release.sh <command> [options]This skill pushes a tag that publishes a public GitHub Release. Do not run tag-push or run unless the user has explicitly asked to cut/tag a release in this turn. When unsure, print the command and let the user run it.
status, and any subcommand with --dry-run.tag-push and run refuse to act without --yes (there is no interactive prompt — be explicit).| Command | What it does |
|---|---|
status | Current version, latest tag, branch, tree state. Read-only. |
bump <version> | Write <version> into apps/desktop/package.json. Local only, no commit. |
tag-push <version> --yes | Commit Release vX.Y.Z, annotated tag vX.Y.Z, push branch + tag. |
run <version> --yes | The one release command: bump → tag-push. |
Options: --dry-run (print without running), --yes (confirm the push), -m/--message <text> (annotated-tag message; default Release vX.Y.Z).
# 1. See where things stand.
.agents/skills/release/scripts/release.sh status
# 2. Preview the whole release without touching anything.
.agents/skills/release/scripts/release.sh run 0.3.0 --yes --dry-run
# 3. Cut it.
.agents/skills/release/scripts/release.sh run 0.3.0 --yesThen watch GitHub Actions → workflow "Release" for the v0.3.0 build; when it finishes, the installers are attached to the v0.3.0 GitHub Release.
0.3.0, 0.3.0-rc.1).tag-push refuses if apps/desktop/package.json isn't already at the target version — run bump first (or use run, which does both).apps/desktop/package.json only, so unrelated working-tree changes are never swept into it.To vet installers before going public, don't use this skill — run the "Release" workflow manually (workflow_dispatch) from the Actions tab with a tag like v0.3.0-rc.1. The workflow derives the temporary desktop app version from this tag, so installer filenames, update metadata, and the app itself use 0.3.0-rc.1 without requiring a version commit. Manual runs publish a draft release you can inspect before making it public.
apps/desktop/package.json — the root and other workspace packages are private with no meaningful version. If a future release needs to version another package, extend VERSION_FILE in scripts/release.sh..agents/skills/ (there is no .claude/skills symlink), so always invoke the script by its .agents/skills/... path.© microsoft, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 1 other file (scripts) in .agents/skills/release of microsoft/Huabu.
Open the folder on GitHubat commit dc0cfa9
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 skillmicrosoft/Huabu | 157 | — | ~1.1k | Automated safety check: Pass | MIT | |
| Release Allpaperboytm/spool | 592 | — | ~1.1k | Automated safety check: Pass | Custom licence | |
| GitHub Actions Supply Chain Pinningasyncapi/generator | 1.1k | — | ~1.9k | Automated safety check: Pass | Apache-2.0 | |
| npm Release Via GitHub Actionsjmfederico/pi-web | 861 | — | ~2.9k | Automated safety check: Pass | MIT | |
| Release Flowromankurnovskii/BrewMate | 301 | — | ~976 | Automated safety check: Pass | MIT | |
| CI Runner Auditapache/magpie | 110 | — | ~2.4k | Automated safety check: Pass | Apache-2.0 |
paperboytm/spool
Publish the complete Spool CLI release train: synchronized versions, npm packages, the GitHub release, and the matching production web deployment.
asyncapi/generator
A skill your agent uses when editing, adding, or reviewing any file under .github/workflows/, or when a CI step installs a CLI tool (npm i -g, npx, pipx, uses: /setup-).
jmfederico/pi-web
A skill your agent uses whenever the user asks for a new npm version, npm release, package release, new release, version bump, publishing to npm, cutting a GitHub release, tagging a release, or…
romankurnovskii/BrewMate
Automate the full application release flow for BrewMate, including committing local changes, bumping version, waiting for GitHub Actions release build, and pushing the in-repo cask update…
apache/magpie
Read-only audit of GitHub Actions runner compatibility for one repository, a repository set, one Apache project, or the full Apache org.
adeze/raindrop-mcp
Publishing and release workflow with semantic-release and GitHub Actions
microsoft/Huabu
Expert code review of current git changes with a senior engineer lens.
microsoft/Huabu
Review the quality of an agent's tool descriptions, system/agent prompts, or SKILL.md files against current agent-engineering best practices.
microsoft/Huabu
Space mental model (the infinite work surface), tool boundaries, and command reference.
microsoft/Huabu
Review the Huabu operate agent's three steering artifacts at their fixed repo locations — system prompt, tool descriptions, and skills.
microsoft/Huabu
Coordinate one or more GitHub issues through isolated Git worktrees, durable Huabu Tasks, and dedicated Fixing Agent Threads.
microsoft/Huabu
Create and revise editable slide decks, PowerPoint files, and slide images with DeepV.
Works with
Categories
Use ONLY when the user explicitly asks to cut/publish a Huabu desktop release or tag a version. Release is an agent skill from microsoft/Huabu, published by the product's own GitHub organization. Use ONLY when the user explicitly asks to cut/publish a Huabu desktop release or tag a version.
Release fits situations like: explicitly asks to cut/publish a Huabu desktop release.
Run `npx skills add microsoft/Huabu --skill release -a claude-code`. Or copy the skill folder (.agents/skills/release in microsoft/Huabu) into .claude/skills/release in your project. Claude Code loads it when a task matches its description.
Run `npx skills add microsoft/Huabu --skill release -a codex`. Or copy the skill folder (.agents/skills/release in microsoft/Huabu) into .agents/skills/release in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add microsoft/Huabu --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.
Going by SKILL.md and its folder, Release needs a shell for the scripts in its folder. Our summary lists: A Bash shell.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
Release is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.1k tokens (SKILL.md is roughly 4.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Release: Release All (paperboytm/spool, 592 stars), GitHub Actions Supply Chain Pinning (asyncapi/generator, 1.1k stars), npm Release Via GitHub Actions (jmfederico/pi-web, 861 stars) and Release Flow (romankurnovskii/BrewMate, 301 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
microsoft (a GitHub organization, an official publisher) maintains it in microsoft/Huabu, which has 157 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on October 7, 2026.
Source: microsoft/Huabu on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.