Update V8 Version
openinterpreter/openinterpreter
Bumps the pinned v8 and rusty_v8 versions in Codex, validates the release-candidate path with the v8-canary check, and traces failures to upstream build changes.
Review Rust module boundaries and implicit coupling using cargo-coupling and source evidence.
MITAuto-check passed
Install Coupling Review
$ npx skills add nwiizo/cargo-coupling --skill coupling-review -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install nwiizo/cargo-coupling coupling-review --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/coupling-review .claude/skills/coupling-review && 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 "coupling-review" agent skill from https://github.com/nwiizo/cargo-coupling/tree/main/.agents/skills/coupling-review into .claude/skills/coupling-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "coupling-review", 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/coupling-reviewType 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 coupling-review -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install nwiizo/cargo-coupling coupling-review --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/coupling-review .agents/skills/coupling-review && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "coupling-review" agent skill from https://github.com/nwiizo/cargo-coupling/tree/main/.agents/skills/coupling-review into .agents/skills/coupling-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "coupling-review", 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 coupling-review -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install nwiizo/cargo-coupling coupling-review --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/coupling-review .cursor/skills/coupling-review && 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 "coupling-review" agent skill from https://github.com/nwiizo/cargo-coupling/tree/main/.agents/skills/coupling-review into .cursor/skills/coupling-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "coupling-review", 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/coupling-review--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 coupling-review -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install nwiizo/cargo-coupling coupling-review --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/coupling-review .gemini/skills/coupling-review && 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 "coupling-review" agent skill from https://github.com/nwiizo/cargo-coupling/tree/main/.agents/skills/coupling-review into .gemini/skills/coupling-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "coupling-review", 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 coupling-reviewInstalls 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 coupling-review -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/coupling-review .github/skills/coupling-review && 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 "coupling-review" agent skill from https://github.com/nwiizo/cargo-coupling/tree/main/.agents/skills/coupling-review into .github/skills/coupling-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "coupling-review", 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 coupling-review -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 coupling-review --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/coupling-review .opencode/skills/coupling-review && 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 "coupling-review" agent skill from https://github.com/nwiizo/cargo-coupling/tree/main/.agents/skills/coupling-review into .opencode/skills/coupling-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "coupling-review", 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
coupling-review- GitHub stars
- 112
- Token cost
- ~425 tokens
- SKILL.md length
- 191 words
- Files
- 1
- Skills in repo
- 14
- Repo updated
- First seen
- Licence
- MIT
At a glance
Review Rust module boundaries and implicit coupling using cargo-coupling and source evidence.
- Focused modularity reviews
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Not prose reviews
What it does
Coupling Review is an agent skill from nwiizo/cargo-coupling. Review Rust module boundaries and implicit coupling using cargo-coupling and source evidence. Use for focused modularity reviews, not prose reviews.
Its SKILL.md is about 430 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
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
- Focused modularity reviews
- Not prose reviews
Example prompts
- “/coupling-review”
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 (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
Coupling Review loads about 425 tokens when it runs. Until then it costs about 41 tokens; SKILL.md has 191 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). 191 words, ~425 tokens.
Download SKILL.mdSave it as
.claude/skills/coupling-review/SKILL.md (or your agent's skills folder).- name
- coupling-review
- description
- Review Rust module boundaries and implicit coupling using cargo-coupling and source evidence. Use for focused modularity reviews, not prose reviews.
- argument-hint
- [path]
Modularity Review
Review the requested scope (default ./src) for changes that would force unrelated
modules to change together. Reuse a current report or obtain one:
rtk proxy cargo run -- coupling --ai ./srcRead the target's .coupling.toml and the source behind consequential findings.
Use the balance model for interpretation. Missing
subdomain configuration is uncertainty to explain, not a reason to block a review
or invent business classifications.
Focus semantic inspection on knowledge shared across boundaries: duplicated rules, shared constants or ordering assumptions, and co-changing files without an AST edge. Separate code evidence from assumptions about teams, deployments, or runtime behavior that static analysis cannot establish. Check the analysis manifest before calling a report clean.
Prioritize supported findings by change impact and essential volatility. Preserve expected entrypoint fan-out, stable hubs, and re-export facades. Keep configuration and history comparable; grade improvement alone is not evidence of better design.
Report findings with file locations, shared knowledge, likely impact, and a specific recommendation. Include sound design choices and relevant blind spots; omit empty sections. Use history or baseline analysis only when trend or PR context matters. The review is complete when its findings and limits are supported; implementation is a separate user-requested action.
© 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/coupling-review of nwiizo/cargo-coupling.
Open the folder on GitHubat commit 8ef1441
Compare with similar skills
Coupling Review 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 |
|---|---|---|---|---|---|---|
| Coupling Review this skillnwiizo/cargo-coupling | 112 | — | ~425 | Automated safety check: Pass | MIT | |
| Update V8 Versionopeninterpreter/openinterpreter | 69k | 2 repos | ~845 | Automated safety check: Pass | Apache-2.0 | |
| Firecrawl Page Scrape Integrationfirecrawl/firecrawl | 190k | 1 repos | ~944 | Automated safety check: Pass | ISC | |
| Migrate Core Code to Submodulestinyhumansai/openhuman | 42k | — | ~2.6k | Automated safety check: Pass | GPL-3.0 | |
| Rust TDD Workflowrtk-ai/rtk | 83k | — | ~753 | Automated safety check: Notes | Apache-2.0 | |
| OpenLogi macOS Permissions TriageAprilNEA/OpenLogi | 23k | — | ~2.5k | Automated safety check: Notes | Apache-2.0 |
Similar skills
Firecrawl Page Scrape Integration
firecrawl/firecrawl
Adds Firecrawl's /scrape endpoint to application code to pull markdown, HTML, links, screenshots or structured data from a single known URL.
Migrate Core Code to Submodules
tinyhumansai/openhuman
Plans and carries out moving non-host-specific code and its tests from the OpenHuman core into vendored tiny submodule libraries, then releases the submodule and re-pins the host.
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.
OpenLogi macOS Permissions Triage
AprilNEA/OpenLogi
Decides whether an OpenLogi device problem on macOS is a privacy-permission (TCC) problem, using agent log lines, and says which identity needs which grant.
Rust Best Practices
farm-fe/farm
Guide for writing idiomatic Rust code based on Apollo GraphQL's best practices handbook.
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.
Hotspots
nwiizo/cargo-coupling
Rank a Rust project's refactoring candidates using cargo-coupling hotspots.
Related
Works with
Questions about Coupling Review
What does Coupling Review do?
Review Rust module boundaries and implicit coupling using cargo-coupling and source evidence. Coupling Review is an agent skill from nwiizo/cargo-coupling. Review Rust module boundaries and implicit coupling using cargo-coupling and source evidence.
When should I use Coupling Review?
Coupling Review fits situations like: focused modularity reviews; not prose reviews.
How do I install Coupling Review in Claude Code?
Run `npx skills add nwiizo/cargo-coupling --skill coupling-review -a claude-code`. Or copy the skill folder (.agents/skills/coupling-review in nwiizo/cargo-coupling) into .claude/skills/coupling-review in your project. Claude Code loads it when a task matches its description.
How do I install Coupling Review in Codex?
Run `npx skills add nwiizo/cargo-coupling --skill coupling-review -a codex`. Or copy the skill folder (.agents/skills/coupling-review in nwiizo/cargo-coupling) into .agents/skills/coupling-review in your project. Codex loads it when a task matches its description.
Can I use Coupling Review 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 coupling-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/coupling-review, .gemini/skills/coupling-review, .github/skills/coupling-review and .opencode/skills/coupling-review in your project.
What does Coupling Review need to run?
SKILL.md names no scripts, command-line tools or credentials: Coupling Review is instructions for the agent only.
Does Coupling Review 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 Coupling Review 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 Coupling Review use?
Coupling Review 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 Coupling Review use?
About 425 tokens (SKILL.md is roughly 1.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 Coupling Review?
Skills that share tags, products or a category with Coupling Review: Update V8 Version (openinterpreter/openinterpreter, 69k stars), Firecrawl Page Scrape Integration (firecrawl/firecrawl, 190k stars), Migrate Core Code to Submodules (tinyhumansai/openhuman, 42k stars) and Rust TDD Workflow (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 Coupling Review?
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.