Reproduce macOS Python Flavors
Nuitka/Nuitka
Reproduce macOS Nuitka issues across Python distributions and GitHub Actions Python packaging.
Cuts a new versioned release of the Clawd Tank macOS menu bar app.
Install Releasing
$ npx skills add marciogranzotto/clawd-tank --skill releasing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install marciogranzotto/clawd-tank releasing --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/marciogranzotto/clawd-tank.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/releasing .claude/skills/releasing && 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 "releasing" agent skill from https://github.com/marciogranzotto/clawd-tank/tree/master/.claude/skills/releasing into .claude/skills/releasing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "releasing", 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/marciogranzotto/clawd-tank/tree/master/.claude/skills/releasingType 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 marciogranzotto/clawd-tank --skill releasing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install marciogranzotto/clawd-tank releasing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/marciogranzotto/clawd-tank.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/releasing .agents/skills/releasing && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "releasing" agent skill from https://github.com/marciogranzotto/clawd-tank/tree/master/.claude/skills/releasing into .agents/skills/releasing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "releasing", 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 marciogranzotto/clawd-tank --skill releasing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install marciogranzotto/clawd-tank releasing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/marciogranzotto/clawd-tank.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/releasing .cursor/skills/releasing && 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 "releasing" agent skill from https://github.com/marciogranzotto/clawd-tank/tree/master/.claude/skills/releasing into .cursor/skills/releasing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "releasing", 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/marciogranzotto/clawd-tank.git --path .claude/skills/releasing--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 marciogranzotto/clawd-tank --skill releasing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install marciogranzotto/clawd-tank releasing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/marciogranzotto/clawd-tank.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/releasing .gemini/skills/releasing && 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 "releasing" agent skill from https://github.com/marciogranzotto/clawd-tank/tree/master/.claude/skills/releasing into .gemini/skills/releasing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "releasing", 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 marciogranzotto/clawd-tank releasingInstalls 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 marciogranzotto/clawd-tank --skill releasing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/marciogranzotto/clawd-tank.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/releasing .github/skills/releasing && 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 "releasing" agent skill from https://github.com/marciogranzotto/clawd-tank/tree/master/.claude/skills/releasing into .github/skills/releasing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "releasing", 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 marciogranzotto/clawd-tank --skill releasing -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install marciogranzotto/clawd-tank releasing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/marciogranzotto/clawd-tank.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/releasing .opencode/skills/releasing && 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 "releasing" agent skill from https://github.com/marciogranzotto/clawd-tank/tree/master/.claude/skills/releasing into .opencode/skills/releasing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "releasing", 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
releasing- GitHub stars
- 165
- Token cost
- ~923 tokens
- SKILL.md length
- 288 words
- Files
- 1
- Skills in repo
- 1
- Repo updated
- First seen
- Licence
- MIT
At a glance
Cuts a new versioned release of the Clawd Tank macOS menu bar app.
- The user asks to release
- SKILL.md covers Critical: do NOT build or zip…, How versioning works, Release workflow and Optional: update your own…
- Calls git and gh
- Publish a release
What it does
Releasing is an agent skill from marciogranzotto/clawd-tank. Cuts a new versioned release of the Clawd Tank macOS menu bar app. Use when the user asks to release, cut a release, publish a release, ship a version, or bump the version. The release is fully automated by a GitHub Actions workflow that triggers on a vX.Y.Z tag push — do NOT build or zip the app manually.
Its SKILL.md is about 920 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in DevOps & Cloud, covering CI/CD. It works with macOS and GitHub Actions. The licence is MIT.
When your agent uses it
- The user asks to release
- Publish a release
- Bump the version
- A vX.Y.Z tag push — do NOT build
Example prompts
- “/releasing”
What it can do on your machine
Read from SKILL.md and the folder at commit a8942d1. 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:
gitgh
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 gh, 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
Releasing loads about 923 tokens when it runs. Until then it costs about 79 tokens; SKILL.md has 288 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 marciogranzotto/clawd-tank at commit a8942d1, republished under its MIT licence (© marciogranzotto). 288 words, ~923 tokens.
Download SKILL.mdSave it as
.claude/skills/releasing/SKILL.md (or your agent's skills folder).- name
- releasing
- description
- Cuts a new versioned release of the Clawd Tank macOS menu bar app. Use when the user asks to release, cut a release, publish a release, ship a version, or bump the version. The release is fully automated by a GitHub Actions workflow that triggers on a vX.Y.Z tag push — do NOT build or zip the app manually.
Releasing Clawd Tank
The macOS app release is fully automated by CI. .github/workflows/release.yml
triggers on any v* tag push and: builds the static simulator, runs py2app,
bundles the simulator into the .app, zips clawd-tank-macos-arm64.zip, and
creates the GitHub release with that asset attached.
The only manual steps are: merge to master, tag vX.Y.Z, push the tag.
Critical: do NOT build or zip manually
host/build.sh and ditto/zip are for local installs only. Running them
to produce a release artifact is wasted work — the workflow rebuilds everything
on the runner. Pushing the tag is the entire release trigger.
How versioning works
There is no hardcoded version string to edit. host/setup.py's
_bake_version() runs git describe --tags --exact-match HEAD at build time:
- HEAD on a clean
vX.Y.Ztag → baked version isvX.Y.Z. - Otherwise →
<branch>+<N>@<sha>[-dirty].
host/clawd_tank_menubar/version.py only reads this (_version_info.py is
generated and gitignored). So "bump the version" = create the git tag.
Tags are semver vX.Y.Z, published as GitHub releases. Decide patch vs minor by
what landed since the last tag — bugfixes only → patch; new user-facing features
→ minor. Confirm the number with the user if unsure:
git log "$(git describe --tags --abbrev=0)"..master --onelineRelease workflow
- [ ] 1. Merge the PR to master (merge commit — matches repo convention)
- [ ] 2. Sync local master
- [ ] 3. Confirm the version number (patch vs minor)
- [ ] 4. Verify the tree is clean (so the baked version isn't "-dirty")
- [ ] 5. Tag vX.Y.Z on master HEAD and push the tag (this triggers CI)
- [ ] 6. Watch the Release workflow finish
- [ ] 7. Edit the release to add a title + notes (CI leaves them blank)
- [ ] 8. Verify the release + asset1–2. Merge and sync (the repo uses merge commits, not squash):
gh pr merge <N> --merge --delete-branch
git checkout master && git pull --ff-only4. Clean-tree check. _version_info.py, host/dist/, host/build/, and
simulator/build-static/ are gitignored, so they don't dirty the tree:
git status --porcelain # must print nothing5. Tag and push — pushing the tag is what triggers the release:
git tag -a vX.Y.Z -m "Clawd Tank vX.Y.Z — <one-line summary>"
git push origin vX.Y.Z6. Watch CI (~2–3 min):
gh run watch "$(gh run list --workflow=release.yml --limit 1 --json databaseId -q '.[0].databaseId')" --exit-status7. Add release notes. The workflow creates the release with a bare vX.Y.Z
title and an empty body. Give it a real title and notes, and include a changelog
compare link:
gh release edit vX.Y.Z \
--title "vX.Y.Z — <theme>" \
--notes "## Highlights
...
**Full changelog:** https://github.com/marciogranzotto/clawd-tank/compare/<prevtag>...vX.Y.Z"8. Verify:
gh release view vX.Y.Z --json tagName,isDraft,assets
# expect: isDraft false, asset clawd-tank-macos-arm64.zip presentOptional: update your own machine
To run the released build locally (not part of publishing):
cd host && ./build.sh --install # rebuilds at the tag, bakes the clean version, copies to /ApplicationsThen kill and relaunch the app so it picks up the new bundle.
© marciogranzotto, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .claude/skills/releasing of marciogranzotto/clawd-tank.
Open the folder on GitHubat commit a8942d1
Compare with similar skills
Releasing 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 |
|---|---|---|---|---|---|---|
| Releasing this skillmarciogranzotto/clawd-tank | 165 | — | ~923 | Automated safety check: Pass | MIT | |
| Reproduce macOS Python FlavorsNuitka/Nuitka | 15k | — | ~1.7k | Automated safety check: Pass | AGPL-3.0 | |
| GitHub Actionstddworks/ClaudeBar | 1.5k | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| CI Workflow Audithewigovens/jayjay | 175 | — | ~703 | Automated safety check: Pass | Custom licence | |
| GitHub Actions Pin Audithewigovens/jayjay | 175 | — | ~558 | Automated safety check: Pass | Custom licence | |
| CI Runner Auditapache/magpie | 114 | — | ~2.4k | Automated safety check: Pass | Apache-2.0 |
Similar skills
GitHub Actions
tddworks/ClaudeBar
Manage ClaudeBar's GitHub Actions CI/CD pipelines: build, test, and release workflows.
CI Workflow Audit
hewigovens/jayjay
Audit GitHub Actions duplication, timing, filters, and gates.
GitHub Actions Pin Audit
hewigovens/jayjay
Audit unpinned GitHub Actions references or related bot PRs.
CI Runner Audit
apache/magpie
Read-only audit of GitHub Actions runner compatibility for one repository, a repository set, one Apache project, or the full Apache org.
Running GitHub Actions Efficiently
kajisho5/ffmpeg-skill
Cut GitHub Actions minutes and wall-clock time without losing coverage — the OS billing multiplier (macOS 10x / Windows 2x / Linux 1x), trigger hygiene that stops push+pullrequest double-firing…
Related
Works with
Categories
Questions about Releasing
What does Releasing do?
Cuts a new versioned release of the Clawd Tank macOS menu bar app. Releasing is an agent skill from marciogranzotto/clawd-tank. Cuts a new versioned release of the Clawd Tank macOS menu bar app.
When should I use Releasing?
Releasing fits situations like: the user asks to release; publish a release; bump the version; A vX.Y.Z tag push — do NOT build.
How do I install Releasing in Claude Code?
Run `npx skills add marciogranzotto/clawd-tank --skill releasing -a claude-code`. Or copy the skill folder (.claude/skills/releasing in marciogranzotto/clawd-tank) into .claude/skills/releasing in your project. Claude Code loads it when a task matches its description.
How do I install Releasing in Codex?
Run `npx skills add marciogranzotto/clawd-tank --skill releasing -a codex`. Or copy the skill folder (.claude/skills/releasing in marciogranzotto/clawd-tank) into .agents/skills/releasing in your project. Codex loads it when a task matches its description.
Can I use Releasing 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 marciogranzotto/clawd-tank --skill releasing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/releasing, .gemini/skills/releasing, .github/skills/releasing and .opencode/skills/releasing in your project.
What does Releasing need to run?
Going by SKILL.md and its folder, Releasing needs the command-line tools its instructions call (git and gh).
Does Releasing access the network?
SKILL.md contains no URLs. Its commands use git and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Releasing 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 Releasing use?
Releasing 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 Releasing use?
About 923 tokens (SKILL.md is roughly 3.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Releasing?
Skills that share tags, products or a category with Releasing: Reproduce macOS Python Flavors (Nuitka/Nuitka, 15k stars), GitHub Actions (tddworks/ClaudeBar, 1.5k stars), CI Workflow Audit (hewigovens/jayjay, 175 stars) and GitHub Actions Pin Audit (hewigovens/jayjay, 175 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Releasing?
marciogranzotto (a GitHub user) maintains it in marciogranzotto/clawd-tank, which has 165 GitHub stars. The repository was last updated on June 2, 2026.
Source: marciogranzotto/clawd-tank on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.