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 nwiizo in nwiizo/cargo-coupling

Prepare or publish a cargo-coupling version when the user requests a release.

MITAuto-check passedTesting & QA

Install Release

skills CLI
$ npx skills add nwiizo/cargo-coupling --skill release -a claude-code

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

GitHub CLI
$ gh skill install nwiizo/cargo-coupling 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/nwiizo/cargo-coupling.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/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
111
Token cost
~491 tokens
SKILL.md length
216 words
Files
1
Skills in repo
12
Repo updated
First seen
Licence
MIT

At a glance

Prepare or publish a cargo-coupling version when the user requests a release.

  • Requests a release
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Release is an agent skill from nwiizo/cargo-coupling. Prepare or publish a cargo-coupling version when the user requests a release.

Its SKILL.md is about 490 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 Testing & QA. The repository describes itself as: A coupling analysis tool for Rust projects - measuring the 'right distance' in your code. The licence is MIT.

When your agent uses it

  • Requests a release

Example prompts

  • “/release”

What it can do on your machine

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

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    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 491 tokens when it runs. Until then it costs about 21 tokens; SKILL.md has 216 words of instructions outside code blocks.

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

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 nwiizo/cargo-coupling at commit aa0d18b, republished under its MIT licence (© nwiizo). 216 words, ~491 tokens.

Download SKILL.mdSave it as .claude/skills/release/SKILL.md (or your agent's skills folder).
name
release
description
Prepare or publish a cargo-coupling version when the user requests a release.
argument-hint
[version] [prepare or publish]

Release cargo-coupling

Match the requested version and publication scope. A preparation request ends with verified local artifacts; a publish request includes the authorized release commit, tag, push, and publication verification. Carry existing authorization forward. Resolve a missing version before changing release metadata; meanwhile inspect the branch, remote, status, and current release workflow.

Update Cargo.toml and refresh Cargo.lock without upgrading unrelated dependencies. Run the required checks against the final release state:

bash
rtk cargo fmt --all -- --check
rtk cargo clippy --locked --all-targets --all-features -- -D warnings
rtk cargo test --locked --all-features
rtk cargo build --locked --release

Before publication, verify the staged diff, intended branch and remote, matching manifest/lockfile versions, and that the tag does not already identify a different release. Preserve unrelated work. Use an annotated vX.Y.Z tag on the verified release commit; the commit message is chore: release vX.Y.Z. Push only the intended branch and tag to the verified remote; never replace an existing release tag.

Pushing a v* tag triggers .github/workflows/release.yml, which publishes to crates.io and creates a GitHub release. Check both outcomes before reporting publication complete. If publication fails or is uncertain, inspect the workflow and registry state before retrying; do not create another version or move a tag to bypass the failure.

The optional Claude hook in .claude/settings.json checks formatting and lint for matching commit commands. It does not establish that all release checks ran in another host. Reuse successful current checks while the release state is unchanged.

© nwiizo, 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/release of nwiizo/cargo-coupling.

Open the folder on GitHubat commit aa0d18b

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 skillnwiizo/cargo-coupling111—~491Automated safety check: PassMIT
Web Application Testinganthropics/skills180k51 repos~966Automated safety check: PassApache-2.0
Diagnosing Bugsfossasia/eventyay-interpretation1.6k32 repos~2.1kAutomated safety check: PassApache-2.0
TDDpietheinstrengholt/rssmonster56430 repos~906Automated safety check: PassMIT
TDD WorkflowhellangleZ/burn-in-cceverywhere-ralph11211 repos~2.4kAutomated safety check: PassNone
TDDsanity-io/sanity6.4k20 repos~1kAutomated safety check: PassMIT

Similar skills

  • Web Application Testing

    anthropics/skills

    Official

    Tests local web applications with Python Playwright scripts, checking frontend behavior, capturing screenshots and reading browser console logs.

    180k GitHub starsUsed in 51 repos~966 tokens
    Testing & QAAuto-check passed

  • Diagnosing Bugs

    fossasia/eventyay-interpretation

    Diagnosis loop for hard bugs and performance regressions. An agent skill from fossasia/eventyay-interpretation.

    1.6k GitHub starsUsed in 32 repos~2.1k tokens
    Testing & QAAuto-check passed

  • TDD

    pietheinstrengholt/rssmonster

    Test-driven development. An agent skill from pietheinstrengholt/rssmonster.

    564 GitHub starsUsed in 30 repos~906 tokens
    Testing & QAAuto-check passed

  • TDD Workflow

    hellangleZ/burn-in-cceverywhere-ralph

    A skill your agent uses when writing new features, fixing bugs, or refactoring code.

    112 GitHub starsUsed in 11 repos~2.4k tokens
    Testing & QAAuto-check passed

  • TDD

    sanity-io/sanity

    Official

    Test-driven development with red-green-refactor loop. An agent skill from sanity-io/sanity.

    6.4k GitHub starsUsed in 20 repos~1k tokens
    Testing & QAAuto-check passed

  • Context Driven Development

    Ibrahim-3d/orchestrator-supaconductor

    A skill your agent uses when working with Conductor's context-driven development methodology, managing project context artifacts, or understanding the relationship between product.md, tech-stack.md…

    380 GitHub starsUsed in 9 repos~2.9k tokens
    Testing & QAAuto-check passed

More from nwiizo/cargo-coupling

All 12 skills in this repo

  • Balanced Coupling

    nwiizo/cargo-coupling

    Interpret cargo-coupling findings using Khononov's strength, distance, and volatility model.

    111 GitHub stars~516 tokensUpdated today
    Auto-check passed

  • Cargo Coupling

    nwiizo/cargo-coupling

    Explain cargo-coupling CLI options and .coupling.toml configuration.

    111 GitHub stars~290 tokensUpdated today
    Auto-check passed

  • Analyze

    nwiizo/cargo-coupling

    Run cargo-coupling and interpret a Rust project's coupling report, history, or baseline diff.

    111 GitHub stars~354 tokensUpdated today
    Auto-check passed

  • Check Balance

    nwiizo/cargo-coupling

    Check a Rust project's coupling health summary or run a requested CI quality gate.

    111 GitHub stars~307 tokensUpdated today
    Auto-check passed

  • Hotspots

    nwiizo/cargo-coupling

    Rank a Rust project's refactoring candidates using cargo-coupling hotspot results.

    111 GitHub stars~260 tokensUpdated today
    Auto-check passed

  • Mutants

    nwiizo/cargo-coupling

    Run cargo-mutants on selected Rust code and investigate gaps in tests revealed by surviving mutations.

    111 GitHub stars~414 tokensUpdated today
    Auto-check: notes

Categories

Questions about Release

What does Release do?

Prepare or publish a cargo-coupling version when the user requests a release. Release is an agent skill from nwiizo/cargo-coupling. Prepare or publish a cargo-coupling version when the user requests a release.

When should I use Release?

Release fits situations like: requests a release.

How do I install Release in Claude Code?

Run `npx skills add nwiizo/cargo-coupling --skill release -a claude-code`. Or copy the skill folder (.claude/skills/release in nwiizo/cargo-coupling) 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 nwiizo/cargo-coupling --skill release -a codex`. Or copy the skill folder (.claude/skills/release in nwiizo/cargo-coupling) 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 nwiizo/cargo-coupling --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?

SKILL.md names no scripts, command-line tools or credentials: Release is instructions for the agent only.

Does Release access the network?

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.

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 491 tokens (SKILL.md is roughly 2k 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: Web Application Testing (anthropics/skills, 180k stars), Diagnosing Bugs (fossasia/eventyay-interpretation, 1.6k stars), TDD (pietheinstrengholt/rssmonster, 564 stars) and TDD Workflow (hellangleZ/burn-in-cceverywhere-ralph, 112 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Release?

nwiizo (a GitHub user) maintains it in nwiizo/cargo-coupling, which has 111 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on October 8, 2026.

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