Agent skill

E2E Test

by nwiizo in nwiizo/cargo-coupling

Verify cargo-coupling CLI behavior end to end using disposable Rust fixtures.

MITAuto-check passedTesting & QA

Install E2E Test

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

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

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

At a glance

Verify cargo-coupling CLI behavior end to end using disposable Rust fixtures.

  • Tasks that involve End-to-end testing
  • Calls cargo

What it does

E2E Test is an agent skill from nwiizo/cargo-coupling. Verify cargo-coupling CLI behavior end to end using disposable Rust fixtures.

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

It sits in Testing & QA, covering End-to-end testing. 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

  • Tasks that involve End-to-end testing

Example prompts

  • “/e2e-test”

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

    Shell commands in SKILL.md call:

    • cargo

    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

E2E Test loads about 436 tokens when it runs. Until then it costs about 22 tokens; SKILL.md has 222 words of instructions outside code blocks.

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

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). 222 words, ~436 tokens.

Download SKILL.mdSave it as .claude/skills/e2e-test/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
e2e-test
description
Verify cargo-coupling CLI behavior end to end using disposable Rust fixtures.
argument-hint
[--quick] [--verbose] [--keep] [--web] [scenario]

End-to-End Verification

Exercise the requested CLI behavior with observable assertions. Use existing regression tests when they cover the request; use test-scenarios.md for a minimal external project and checks for module paths, test exclusion, and config loading. Run this package's cargo run from its checkout, passing the fixture path as the analysis target.

Create a unique fixture with mktemp -d; never remove or reuse a fixed /tmp path. Local fixtures are disposable and have no production access. Continue their setup, execution, and checks without repeated approval. Remove only resources created by this run, retaining them when requested with --keep.

Select coverage from the request:

  • --quick: nested modules, valid JSON, and summary output.
  • Default: also verify test exclusion, configuration, and requested output modes.
  • --verbose: include commands, assertions, and observed values in the report.
  • --web: add server/API checks using the Web UI rules; stop only the server started for this run.

These are skill options, not flags to forward to cargo-coupling. Run repository checks when required by the task; a smoke test does not establish full E2E coverage. Fix and recheck failures caused by an implementation the user asked you to make. For a test-only request, report failures with reproduction details.

Finish with actual results, skipped scenarios, exit statuses, and retained fixture paths. Do not report checks as passed merely because a command produced output.

© 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/e2e-test of nwiizo/cargo-coupling.

  • SKILL.md
  • test-scenarios.md

Open the folder on GitHubat commit aa0d18b

Compare with similar skills

E2E Test 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.

E2E Test compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
E2E Test this skillnwiizo/cargo-coupling111—~436Automated safety check: PassMIT
Warp Integration Test Videowarpdotdev/warp65k1 repos~2.6kAutomated safety check: PassAGPL-3.0
Hydra Devstreamband/hydra-srt146—~995Automated safety check: PassApache-2.0
Kaniop Developmentpando85/kaniop130—~3.1kAutomated safety check: PassAGPL-3.0
Test Specialisttravisjneuman/.claude101—~3.7kAutomated safety check: PassMIT
Desktop App Driving with Reticlereticlehq/reticle1.2k—~1.3kAutomated safety check: PassApache-2.0

Similar skills

  • Records screenshots and video from Warp's Rust integration-test harness, with the commands and environment variables to run a named test and review its artifacts.

    65k GitHub starsUsed in 1 repo~2.6k tokens
    Testing & QAAuto-check passed
  • Hydra Dev

    streamband/hydra-srt

    Run HydraSRT development workflows: mix q quality gate, Elixir unit/E2E tests, native Rust tests, web Vitest/Playwright, and make dev.

    146 GitHub stars~995 tokensUpdated 22 days ago
    Testing & QAAuto-check passed
  • Kaniop Development

    pando85/kaniop

    Kaniop architecture, Rust controller conventions, commands, testing, and repository workflows.

    130 GitHub stars~3.1k tokensUpdated yesterday
    Testing & QAAuto-check passed
  • Test Specialist

    travisjneuman/.claude

    Test-writing patterns for JS/TS, Python, Go, and Rust (unit, integration, E2E, visual regression).

    101 GitHub stars~3.7k tokensUpdated 2 days ago
    Testing & QAAuto-check passed
  • Drives and verifies Electron or Tauri desktop apps through Reticle, which sees the renderer and the IPC calls that a browser-based testing tool cannot observe.

    1.2k GitHub stars~1.3k tokensUpdated today
    Testing & QAAuto-check passed
  • A skill your agent uses when building Farm locally from source, native bindings or Rust plugin artifacts are missing, or an example/E2E needs local core and plugin artifacts.

    5.6k GitHub stars~857 tokensUpdated 16 days ago
    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
  • 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

Works with

Categories

Questions about E2E Test

What does E2E Test do?

Verify cargo-coupling CLI behavior end to end using disposable Rust fixtures. E2E Test is an agent skill from nwiizo/cargo-coupling. Verify cargo-coupling CLI behavior end to end using disposable Rust fixtures.

When should I use E2E Test?

E2E Test fits situations like: tasks that involve End-to-end testing.

How do I install E2E Test in Claude Code?

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

How do I install E2E Test in Codex?

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

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

What does E2E Test need to run?

Going by SKILL.md and its folder, E2E Test needs the command-line tools its instructions call (cargo).

Does E2E Test 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 E2E Test 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 E2E Test use?

E2E Test 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 E2E Test use?

About 436 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 E2E Test?

Skills that share tags, products or a category with E2E Test: Warp Integration Test Video (warpdotdev/warp, 65k stars), Hydra Dev (streamband/hydra-srt, 146 stars), Kaniop Development (pando85/kaniop, 130 stars) and Test Specialist (travisjneuman/.claude, 101 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains E2E Test?

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.