Find Release
flutter/flutter
A skill to find the lowest Dart and Flutter release containing a given commit.
Explain a specific cargo-coupling issue type or finding, its detection limits, and possible remedies.
MITAuto-check passed
Install Explain Issue
$ npx skills add nwiizo/cargo-coupling --skill explain-issue -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install nwiizo/cargo-coupling explain-issue --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/nwiizo/cargo-coupling.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/explain-issue .claude/skills/explain-issue && 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 "explain-issue" agent skill from https://github.com/nwiizo/cargo-coupling/tree/main/.agents/skills/explain-issue into .claude/skills/explain-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "explain-issue", 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/nwiizo/cargo-coupling/tree/main/.agents/skills/explain-issueType 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 nwiizo/cargo-coupling --skill explain-issue -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install nwiizo/cargo-coupling explain-issue --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nwiizo/cargo-coupling.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/explain-issue .agents/skills/explain-issue && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "explain-issue" agent skill from https://github.com/nwiizo/cargo-coupling/tree/main/.agents/skills/explain-issue into .agents/skills/explain-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "explain-issue", 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 nwiizo/cargo-coupling --skill explain-issue -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install nwiizo/cargo-coupling explain-issue --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nwiizo/cargo-coupling.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/explain-issue .cursor/skills/explain-issue && 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 "explain-issue" agent skill from https://github.com/nwiizo/cargo-coupling/tree/main/.agents/skills/explain-issue into .cursor/skills/explain-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "explain-issue", 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/nwiizo/cargo-coupling.git --path .agents/skills/explain-issue--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 nwiizo/cargo-coupling --skill explain-issue -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install nwiizo/cargo-coupling explain-issue --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nwiizo/cargo-coupling.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/explain-issue .gemini/skills/explain-issue && 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 "explain-issue" agent skill from https://github.com/nwiizo/cargo-coupling/tree/main/.agents/skills/explain-issue into .gemini/skills/explain-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "explain-issue", 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 nwiizo/cargo-coupling explain-issueInstalls 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 nwiizo/cargo-coupling --skill explain-issue -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/nwiizo/cargo-coupling.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/explain-issue .github/skills/explain-issue && 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 "explain-issue" agent skill from https://github.com/nwiizo/cargo-coupling/tree/main/.agents/skills/explain-issue into .github/skills/explain-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "explain-issue", 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 nwiizo/cargo-coupling --skill explain-issue -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install nwiizo/cargo-coupling explain-issue --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nwiizo/cargo-coupling.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/explain-issue .opencode/skills/explain-issue && 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 "explain-issue" agent skill from https://github.com/nwiizo/cargo-coupling/tree/main/.agents/skills/explain-issue into .opencode/skills/explain-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "explain-issue", 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
explain-issue- GitHub stars
- 112
- Token cost
- ~395 tokens
- SKILL.md length
- 149 words
- Files
- 1
- Skills in repo
- 14
- Repo updated
- First seen
- Licence
- MIT
At a glance
Explain a specific cargo-coupling issue type or finding, its detection limits, and possible remedies.
- Interpretation without requiring a full analysis run
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Explain Issue is an agent skill from nwiizo/cargo-coupling. Explain a specific cargo-coupling issue type or finding, its detection limits, and possible remedies. Use for interpretation without requiring a full analysis run.
Its SKILL.md is about 400 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
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
- Interpretation without requiring a full analysis run
Example prompts
- “/explain-issue”
What it can do on your machine
Read from SKILL.md and the folder at commit 8ef1441. 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.
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
Explain Issue loads about 395 tokens when it runs. Until then it costs about 44 tokens; SKILL.md has 149 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 nwiizo/cargo-coupling at commit 8ef1441, republished under its MIT licence (© nwiizo). 149 words, ~395 tokens.
Download SKILL.mdSave it as
.claude/skills/explain-issue/SKILL.md (or your agent's skills folder).- name
- explain-issue
- description
- Explain a specific cargo-coupling issue type or finding, its detection limits, and possible remedies. Use for interpretation without requiring a full analysis run.
- argument-hint
- [issue type or finding]
Explain a Coupling Issue
Explain what the requested finding means, what change it could make difficult, and whether the available evidence supports acting on it. Use a small Rust example when it clarifies the user's question; do not require a before/after example for every explanation.
For names and descriptions, inspect issue_type.rs. Read only the relevant detector when explaining exact conditions or severity:
- coupling.rs: strength, distance, volatility.
- patterns.rs: module-level structural patterns.
- signals.rs: temporal and volatility diagnostics.
- external_crates.rs: external dependencies.
Use current thresholds and the target project's configuration. The balance model explains the conceptual tradeoffs; its qualitative table is not a replacement for detection code.
Include relevant exceptions such as entrypoints, stable hubs, and re-export facades. Recommend a remedy only when it addresses the demonstrated problem; traits, facades, and module splits are options, not default fixes. No analysis run is needed for a conceptual question that the available evidence already answers.
© 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 .agents/skills/explain-issue of nwiizo/cargo-coupling.
Open the folder on GitHubat commit 8ef1441
Compare with similar skills
Explain Issue 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 |
|---|---|---|---|---|---|---|
| Explain Issue this skillnwiizo/cargo-coupling | 112 | — | ~395 | Automated safety check: Pass | MIT | |
| Find Releaseflutter/flutter | 180k | — | ~545 | Automated safety check: Pass | BSD-3-Clause | |
| Fd Findpenpot/penpot | 61k | — | ~882 | Automated safety check: Pass | MPL-2.0 | |
| Logic Explainsickn33/agentic-awesome-skills | 47k | 1 repos | ~894 | Automated safety check: Pass | MIT | |
| Faceless Explainer Videoheygen-com/hyperframes | 60k | 3 repos | ~7.7k | Automated safety check: Notes | Apache-2.0 | |
| PR Explainermastra-ai/mastra | 29k | — | ~1.4k | Automated safety check: Pass | Custom licence |
Similar skills
Fd Find
penpot/penpot
A fast and user-friendly alternative to 'find' - simple syntax, smart defaults, respects gitignore.
Logic Explain
sickn33/agentic-awesome-skills
Explain what a specific piece of code actually does for a given input by producing a step-by-step execution trace (interprocedural, with name resolution and type transitions).
Faceless Explainer Video
heygen-com/hyperframes
Turns an article, notes or a topic brief into an explainer video whose visuals are invented per scene, built frame by frame in HyperFrames with no footage.
PR Explainer
mastra-ai/mastra
A skill your agent uses when creating an approachable, self-contained HTML review aid for a pull request; explaining what changed, why it matters, how it works, and how it fits into the broader…
Understand Explain
Egonex-AI/Understand-Anything
Gives an in-depth explanation of one file, function or module by reading the project's knowledge graph and checking that the graph is still fresh.
More from nwiizo/cargo-coupling
All 14 skills in this repoBalanced Coupling
nwiizo/cargo-coupling
Interpret coupling tradeoffs using Khononov's strength, distance, and volatility model.
Release
nwiizo/cargo-coupling
Prepare or publish a cargo-coupling version when the user requests a release.
Similarity
nwiizo/cargo-coupling
Inspect Rust duplicate-code candidates with similarity-rs. An agent skill from nwiizo/cargo-coupling.
Cargo Coupling
nwiizo/cargo-coupling
Explain cargo-coupling CLI options and .coupling.toml configuration.
Check Balance
nwiizo/cargo-coupling
Check a Rust project's cargo-coupling health grade or run a requested CI gate.
Coupling Review
nwiizo/cargo-coupling
Review Rust module boundaries and implicit coupling using cargo-coupling and source evidence.
Questions about Explain Issue
What does Explain Issue do?
Explain a specific cargo-coupling issue type or finding, its detection limits, and possible remedies. Explain Issue is an agent skill from nwiizo/cargo-coupling. Explain a specific cargo-coupling issue type or finding, its detection limits, and possible remedies.
When should I use Explain Issue?
Explain Issue fits situations like: interpretation without requiring a full analysis run.
How do I install Explain Issue in Claude Code?
Run `npx skills add nwiizo/cargo-coupling --skill explain-issue -a claude-code`. Or copy the skill folder (.agents/skills/explain-issue in nwiizo/cargo-coupling) into .claude/skills/explain-issue in your project. Claude Code loads it when a task matches its description.
How do I install Explain Issue in Codex?
Run `npx skills add nwiizo/cargo-coupling --skill explain-issue -a codex`. Or copy the skill folder (.agents/skills/explain-issue in nwiizo/cargo-coupling) into .agents/skills/explain-issue in your project. Codex loads it when a task matches its description.
Can I use Explain Issue 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 explain-issue -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/explain-issue, .gemini/skills/explain-issue, .github/skills/explain-issue and .opencode/skills/explain-issue in your project.
What does Explain Issue need to run?
SKILL.md names no scripts, command-line tools or credentials: Explain Issue is instructions for the agent only.
Does Explain Issue 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 Explain Issue 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 Explain Issue use?
Explain Issue 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 Explain Issue use?
About 395 tokens (SKILL.md is roughly 1.6k 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 Explain Issue?
Skills that share tags, products or a category with Explain Issue: Find Release (flutter/flutter, 180k stars), Fd Find (penpot/penpot, 61k stars), Logic Explain (sickn33/agentic-awesome-skills, 47k stars) and Faceless Explainer Video (heygen-com/hyperframes, 60k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Explain Issue?
nwiizo (a GitHub user) maintains it in nwiizo/cargo-coupling, which has 112 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on October 10, 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.