From rust-toolkit
This skill should be used when the user asks to "run clippy", "lint with clippy", "show clippy warnings", "fix clippy lints", or "run cargo clippy", or when the user wants a Rust lint pass with the full clippy ruleset enabled.
How this skill is triggered — by the user, by Claude, or both
Slash command
/rust-toolkit:clippyThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Run clippy lint checks with `cargo clippy`.
Run clippy lint checks with cargo clippy.
--manifest-path <path>/Cargo.toml to target that project.cargo clippy --manifest-path <path>/Cargo.toml -- -W clippy::all 2>&1
If no path, just:
cargo clippy -- -W clippy::all 2>&1
clippy::needless_return, clippy::redundant_closure).cargo clippy --explain <lint_name>.cargo clippy --fix --allow-dirty -- -W clippy::all 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: lint. 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 /clippy 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.