From rust-toolkit
This skill should be used when the user asks to "run cargo check", "check for compile errors", "see if this compiles", "verify the rust build", or wants a fast compile-only verification of a Rust project without producing binaries.
How this skill is triggered — by the user, by Claude, or both
Slash command
/rust-toolkit:checkThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Check a Rust project for compile errors with `cargo check`.
Check a Rust project for compile errors with cargo check.
--manifest-path <path>/Cargo.toml.cargo check --manifest-path <path>/Cargo.toml 2>&1
If no path, just:
cargo check 2>&1
cargo check --all-targets 2>&1
This skill is forward-looking: the canonical triage procedure lives in skills/diagnostic-review/SKILL.md and is invoked via Skill(skill: "rust-toolkit:diagnostic-review") with pass: check. Per-pass invocation wiring lands in a later chore (per the Path B cut-scope decision); for now the skill body above inlines the procedure that matches the legacy /check command behavior.
npx claudepluginhub zaynram/code-marketplace --plugin rust-toolkitGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Synthesizes the current conversation into a structured spec (PRD) and publishes it to the project issue tracker with a ready-for-agent label, without interviewing the user.