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

Analyze

by nwiizo in nwiizo/cargo-coupling

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

MITAuto-check passedTesting & QA

Install Analyze

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

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

GitHub CLI
$ gh skill install nwiizo/cargo-coupling analyze --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/analyze .claude/skills/analyze && 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
analyze
GitHub stars
111
Token cost
~354 tokens
SKILL.md length
156 words
Files
2
Skills in repo
12
Repo updated
First seen
Licence
MIT

At a glance

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

  • Testing & QA work in your project
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Analyze is an agent skill from nwiizo/cargo-coupling. Run cargo-coupling and interpret a Rust project's coupling report, history, or baseline diff.

Its SKILL.md is about 350 tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `output-template.md`).

It sits in Testing & QA. It works with Rust. 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

  • Testing & QA work in your project

Example prompts

  • “/analyze”

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

Analyze loads about 354 tokens when it runs. Until then it costs about 25 tokens; SKILL.md has 156 words of instructions outside code blocks.

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

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). 156 words, ~354 tokens.

Download SKILL.mdSave it as .claude/skills/analyze/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
analyze
description
Run cargo-coupling and interpret a Rust project's coupling report, history, or baseline diff.
argument-hint
[path] [analysis options]

Coupling Analysis

Run the requested analysis from this repository, using ./src when no target is specified. Choose the output mode that answers the request; one report is usually enough. For interpretation, AI output includes the analysis manifest:

bash
rtk proxy cargo run -- coupling --ai ./src

Use command examples for history, baseline, machine-readable output, or other requested modes. Read coupling --help for options not covered there; pass CLI arguments, not slash-command labels.

Explain the reported grade and its rationale, the consequential findings, and the analysis limits. Check relevant source and configuration before turning a signal into a refactoring recommendation. Preserve Git history, thresholds, and subdomain classification when comparing results; never change them to improve the grade.

Use the balance model when a finding needs semantic interpretation. The report example is optional for a detailed report. A summary request needs only the result and material limits. Analysis is complete when the requested results and supporting evidence are explained; implement changes when the user also requests them.

© 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

SKILL.md and 1 other file in .claude/skills/analyze of nwiizo/cargo-coupling.

  • SKILL.md
  • output-template.md

Open the folder on GitHubat commit aa0d18b

Compare with similar skills

Analyze 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.

Analyze compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Analyze this skillnwiizo/cargo-coupling111—~354Automated safety check: PassMIT
Rust TDD Workflowrtk-ai/rtk83k—~753Automated safety check: NotesApache-2.0
Remote Executor Integration Testsopeninterpreter/openinterpreter69k2 repos~842Automated safety check: PassApache-2.0
Apple Container Test RunnerRustPython/RustPython22k—~467Automated safety check: PassMIT
RTK Filter TDD in Rustrtk-ai/rtk83k—~1.9kAutomated safety check: NotesApache-2.0
OpenLogi Device Fixture ContributionAprilNEA/OpenLogi23k—~1.2kAutomated safety check: PassApache-2.0

Similar skills

  • Rust TDD Workflow

    rtk-ai/rtk

    Enforces red-green-refactor for Rust work, with idiomatic test patterns, a naming convention and a pre-commit gate of cargo fmt, clippy and test.

    83k GitHub stars~753 tokensUpdated today
    Testing & QAAuto-check: notes

  • Remote Executor Integration Tests

    openinterpreter/openinterpreter

    Explains how to run agent integration tests against remote executors, using Docker for Linux or Wine for Windows, and how to opt tests in or skip them.

    69k GitHub starsUsed in 2 repos~842 tokens
    Testing & QAAuto-check passed

  • Apple Container Test Runner

    RustPython/RustPython

    Runs RustPython tests inside a Linux container built with Apple's container CLI, so macOS users can compare Linux results with their local ones.

    22k GitHub stars~467 tokensUpdated today
    Testing & QAAuto-check passed

  • RTK Filter TDD in Rust

    rtk-ai/rtk

    Enforces red-green-refactor for new RTK output filters in Rust, using real captured fixtures, snapshot tests with insta and token-savings assertions.

    83k GitHub stars~1.9k tokensUpdated today
    Testing & QAAuto-check: notes

  • OpenLogi Device Fixture Contribution

    AprilNEA/OpenLogi

    Guides recording, privacy review and offline verification of OpenLogi device fixtures with the fixture contribute and verify commands, without treating replay as proof of hardware behavior.

    23k GitHub stars~1.2k tokensUpdated today
    Testing & QAAuto-check passed

  • Testing OpenLogi UI

    AprilNEA/OpenLogi

    Verifies OpenLogi's native GPUI interface with focused tests, the component gallery and a mock agent, choosing the evidence that fits each change.

    23k GitHub stars~1.1k tokensUpdated today
    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

  • Release

    nwiizo/cargo-coupling

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

    111 GitHub stars~491 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

Works with

Categories

Questions about Analyze

What does Analyze do?

Run cargo-coupling and interpret a Rust project's coupling report, history, or baseline diff. Analyze is an agent skill from nwiizo/cargo-coupling. Run cargo-coupling and interpret a Rust project's coupling report, history, or baseline diff.

When should I use Analyze?

Analyze fits situations like: testing & QA work in your project.

How do I install Analyze in Claude Code?

Run `npx skills add nwiizo/cargo-coupling --skill analyze -a claude-code`. Or copy the skill folder (.claude/skills/analyze in nwiizo/cargo-coupling) into .claude/skills/analyze in your project. Claude Code loads it when a task matches its description.

How do I install Analyze in Codex?

Run `npx skills add nwiizo/cargo-coupling --skill analyze -a codex`. Or copy the skill folder (.claude/skills/analyze in nwiizo/cargo-coupling) into .agents/skills/analyze in your project. Codex loads it when a task matches its description.

Can I use Analyze 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 analyze -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/analyze, .gemini/skills/analyze, .github/skills/analyze and .opencode/skills/analyze in your project.

What does Analyze need to run?

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

Does Analyze 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 Analyze 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 Analyze use?

Analyze 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 Analyze use?

About 354 tokens (SKILL.md is roughly 1.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 Analyze?

Skills that share tags, products or a category with Analyze: Rust TDD Workflow (rtk-ai/rtk, 83k stars), Remote Executor Integration Tests (openinterpreter/openinterpreter, 69k stars), Apple Container Test Runner (RustPython/RustPython, 22k stars) and RTK Filter TDD in Rust (rtk-ai/rtk, 83k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Analyze?

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 9, 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.