New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Release

by st0012 in st0012/cctop

A skill your agent uses when cutting or preparing a cctop release - "cut a release", "release vX.Y.Z", "prepare a release", "bump the version and tag", "ship a new version".

MITAuto-check passedMobile

Install Release

skills CLI
$ npx skills add st0012/cctop --skill release -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install st0012/cctop release --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/st0012/cctop.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/release .claude/skills/release && rm -rf skills-src

Use ~/.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/

Facts

Skill name
release
GitHub stars
154
Token cost
~1.4k tokens
SKILL.md length
714 words
Files
1
Skills in repo
7
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when cutting or preparing a cctop release - "cut a release", "release vX.Y.Z", "prepare a release", "bump the version and tag", "ship a new version".

  • Works in 5 steps: Establish the release contract → Bump the version → Confirm green → …
  • Preparing a cctop release - cut a release
  • SKILL.md covers Authorization and checks, 1. Establish the release…, 2. Bump the version and 3. Confirm green, plus 2 more sections
  • Calls git, gh and make

What it does

Release is an agent skill from st0012/cctop. Use when cutting or preparing a cctop release - "cut a release", "release vX.Y.Z", "prepare a release", "bump the version and tag", "ship a new version". Drives proportionate release checks, version bump, CI, tag push, release monitoring, and verification. An explicit release request authorizes the complete release unless the developer asks to stop before publication.

Its SKILL.md is about 1.4k 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 Mobile. It works with Git and macOS. The repository describes itself as: A keyboard-first menubar app to monitor and jump between AI coding sessions — minimum setup required. The licence is MIT.

When your agent uses it

  • Preparing a cctop release - cut a release
  • Prepare a release
  • Bump the version and tag
  • Ship a new version

Example prompts

  • “cut a release”
  • “release vX.Y.Z”
  • “prepare a release”
  • “/release”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Establish the release contract
  2. Bump the version
  3. Confirm green
  4. Tag and monitor the pipeline
  5. Verify

What it can do on your machine

Read from SKILL.md and the folder at commit 4ee2258. 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:

    • git
    • gh
    • make

    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

Release loads about 1.4k tokens when it runs. Until then it costs about 95 tokens; SKILL.md has 714 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~95
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k

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 st0012/cctop at commit 4ee2258, republished under its MIT licence (© st0012). 714 words, ~1,356 tokens.

Download SKILL.mdSave it as .claude/skills/release/SKILL.md (or your agent's skills folder).
name
release
description
Use when cutting or preparing a cctop release - "cut a release", "release vX.Y.Z", "prepare a release", "bump the version and tag", "ship a new version". Drives proportionate release checks, version bump, CI, tag push, release monitoring, and verification. An explicit release request authorizes the complete release unless the developer asks to stop before publication.

Cutting a cctop Release

Releases are triggered by pushing a v* tag. .github/workflows/release.yml then runs: build (arm64 + x86_64, zip + DMG each) -> sign and notarize -> create GitHub Release -> update Sparkle appcast on master -> update Homebrew cask.

Authorization and checks

  • Treat an explicit request to release, cut, or ship a version as authorization for the complete release: assess scope, run proportionate checks, bump and land the version, push the tag, supervise publication, and verify downstream metadata. Do not insert another routine approval gate when all expected checks pass.
  • A request to prepare, assess, or check whether ready is not publication authorization. Stop before the tag and ask for the final go.
  • Before proposing or adding any release check, state its reason in plain language: name the concrete failure or release risk it covers and why the shipped changes make that risk relevant. Do not propose a check merely because an older or larger release used it.
  • Scale checks to the release. Previously approved PR tests are feature evidence; release checks should cover integration, versioning, packaging, and risks introduced by the exact release range. Patch releases should not inherit major-release manual tests without a specific reason.
  • Once an authorized release's checks pass, continue automatically. Stop only when a check fails unexpectedly, the release range/version is ambiguous, unrelated changes appear, publication requires a genuinely new product decision, or the developer asks to pause.
  • Never merge feature PRs; the developer merges them. The approved release bump may land by the agreed repository path.

1. Establish the release contract

  1. Sync and review what's shipping: git pull then git log $(git describe --tags --abbrev=0)..origin/master --oneline.
  2. Propose or confirm the semver bump and a short changelog summary.
  3. State how the bump commit will land. Direct push to master is allowed for this repo; most releases use this path. Use a PR if the developer prefers.
  4. List the release checks and give one concise reason for each. Remove checks whose reason is only habit or duplication of already-approved feature evidence.
  5. If the developer explicitly requested the release and the version/scope are clear, continue. If they only requested preparation/readiness assessment, stop for approval.

2. Bump the version

  • Always use scripts/bump-version.sh <version>; never edit version numbers by hand. The script updates the Xcode project, Config.hookVersion, plugin manifests, packaging, and the site fallback badge together.
  • Run make all (lint + contract + build + test) before committing.
  • Commit Bump version to <version> and land it per step 1.
  • If a PR was used: monitor CI to green, then stop and let the developer merge.
Show full SKILL.md (290 more words)Show less

3. Confirm green

  • Wait for master CI on the bump commit: gh run list --branch master --limit 5, then gh run watch <id>.
  • For an explicitly authorized release, continue to the exact tag as soon as expected checks and master CI pass.
  • For preparation/readiness-only work, report the exact candidate and stop for tag authorization. The tag push publishes the release, appcast update, and cask bump.

4. Tag and monitor the pipeline

bash
git tag v<version> && git push origin v<version>
  • Monitor the Release workflow to completion (gh run watch, or poll gh run list --workflow release.yml with retry/backoff on transient gh failures).
  • Do not name shell variables status; it is readonly in zsh and has silently broken CI watchers before.
  • If any job fails, stop immediately and report the exact failure with logs. Use the signing and appcast rules below for local diagnosis.
Signing and appcast rules
  • Sign Sparkle components without the app's entitlements. Apply entitlements only to the main executable and the app bundle.
  • Sign from the inside out: libraries, inner executables, nested bundles, the main executable, and then the app bundle.
  • Search Sparkle.framework/Versions/B/Autoupdate for executable components. This path has no MacOS directory.
  • Use ./scripts/sign-and-notarize.sh --dry-run dist/cctop.app to inspect signing order.
  • Use --sign-only only for local signing diagnosis. It does not prove notarization.
  • Keep arm64 and x86_64 appcast enclosures in separate <item> elements. Sparkle selects hardware at the item level.
  • If Homebrew does not link the tools, the script searches /opt/homebrew/Caskroom/sparkle/*/bin/ for them.
  • Use SPARKLE_PRIVATE_KEY_FILE=<key> ./scripts/generate-appcast.sh --version <version> arm64.zip x86_64.zip for local appcast diagnosis.

5. Verify

  • gh release view v<version> lists all four assets: cctop-macOS-{arm64,x86_64}.{zip,dmg}.
  • appcast.xml on master has separate arm64 and x86_64 <item> entries for the new version. CI commits this; pull and check.
  • The Homebrew cask job succeeded.
  • Report the release URL and what was verified.

© st0012, 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 .agents/skills/release of st0012/cctop.

Open the folder on GitHubat commit 4ee2258

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.

Release compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Release this skillst0012/cctop154—~1.4kAutomated safety check: PassMIT
Swiftui Patternsrobinebers/openusage4.3k—~3.4kAutomated safety check: PassMIT
Releasenotepadqq/notepadqq2.3k—~2kAutomated safety check: PassGPL-3.0
Releasevaayne/mori303—~1.2kAutomated safety check: PassMIT
macOS Releasefayazara/macos-app-skills675—~1.8kAutomated safety check: PassNone
macOS App Designvaayne/mori303—~789Automated safety check: PassMIT

Similar skills

  • Swiftui Patterns

    robinebers/openusage

    Best practices and example-driven guidance for building native macOS SwiftUI scenes and components, including windows, commands, toolbars, settings, split views, inspectors, menu bar extras, and…

    4.3k GitHub stars~3.4k tokensUpdated 2 days ago
    MobileAuto-check passed

  • Release

    notepadqq/notepadqq

    Release a new Notepadqq version. An agent skill from notepadqq/notepadqq.

    2.3k GitHub stars~2k tokensUpdated 3 days ago
    MobileAuto-check passed

  • Release

    vaayne/mori

    Release workflow for Mori macOS workspace terminal and MoriRemote iOS app.

    303 GitHub stars~1.2k tokensUpdated 2 mo ago
    MobileAuto-check passed

  • macOS Release

    fayazara/macos-app-skills

    Release a native macOS app to GitHub with DMG packaging and Sparkle appcast updates.

    675 GitHub stars~1.8k tokensUpdated 4 mo ago
    MobileAuto-check passed

  • macOS App Design

    vaayne/mori

    A skill your agent uses when designing or building native macOS applications with SwiftUI or AppKit.

    303 GitHub stars~789 tokensUpdated 2 mo ago
    MobileAuto-check passed

  • Build Afm

    scouzi1966/maclocal-api

    Build AFM from scratch — submodules, patches, webui, and Swift build.

    345 GitHub stars~1.8k tokensUpdated 3 days ago
    MobileAuto-check: notes

More from st0012/cctop

  • E2E Session Test

    st0012/cctop

    A skill your agent uses when smoke-testing cctop end to end — verifying a real coding-agent session is tracked and shows in the panel.

    154 GitHub stars~727 tokensUpdated 8 days ago
    Auto-check passed

  • Video Assets

    st0012/cctop

    A skill your agent uses when publishing, replacing, auditing, or linking cctop promo/demo video assets through GitHub Releases, especially the non-latest media-assets release.

    154 GitHub stars~1.4k tokensUpdated 8 days ago
    Auto-check passed

  • Swiftui Debugging

    st0012/cctop

    A skill your agent uses when debugging SwiftUI issues in this macOS app — views not updating, layout problems, unnecessary re-renders, state ownership bugs, Preview crashes, or NSHostingView/NSPanel…

    154 GitHub stars~2k tokensUpdated 8 days ago
    Auto-check passed

  • Video Storyboard

    st0012/cctop

    A skill your agent uses when designing, scripting, or storyboarding a short demo, launch, explainer, or marketing video (especially for a developer tool, app, or SaaS), OR when auditing, critiquing…

    154 GitHub stars~3.4k tokensUpdated 8 days ago
    Auto-check passed

  • Cctop Setup

    st0012/cctop

    A skill your agent uses when cctop-hook command fails or is not found.

    154 GitHub stars~335 tokensUpdated 8 days ago
    Auto-check passed

  • Cctop Restart

    st0012/cctop

    Restart cctop for local development and testing. An agent skill from st0012/cctop.

    154 GitHub stars~395 tokensUpdated 8 days ago
    Auto-check passed

Works with

Categories

Questions about Release

What does Release do?

A skill your agent uses when cutting or preparing a cctop release - "cut a release", "release vX.Y.Z", "prepare a release", "bump the version and tag", "ship a new version". Release is an agent skill from st0012/cctop.Z", "prepare a release", "bump the version and tag", "ship a new version".

When should I use Release?

Release fits situations like: preparing a cctop release - cut a release; prepare a release; bump the version and tag; ship a new version.

How do I install Release in Claude Code?

Run `npx skills add st0012/cctop --skill release -a claude-code`. Or copy the skill folder (.agents/skills/release in st0012/cctop) 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 st0012/cctop --skill release -a codex`. Or copy the skill folder (.agents/skills/release in st0012/cctop) 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 st0012/cctop --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, gh and make).

Does Release 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 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.4k tokens (SKILL.md is roughly 5.4k 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 Release?

Skills that share tags, products or a category with Release: Swiftui Patterns (robinebers/openusage, 4.3k stars), Release (notepadqq/notepadqq, 2.3k stars), Release (vaayne/mori, 303 stars) and macOS Release (fayazara/macos-app-skills, 675 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Release?

st0012 (a GitHub user) maintains it in st0012/cctop, which has 154 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 1, 2026.

Source: st0012/cctop on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.