@abusch/rust-best-practice

[Critical] Best practice for Rust coding. Always activate this skill before authoring Rust code or answering questions about Rust.

skillclaude

Install

agr install @abusch/rust-best-practice --target claude

Writes 1 file into .claude/skills/, pinned to git-cd438166.

.claude/skills/rust-best-practice/SKILL.md

Document

name: rust-best-practice description: [Critical] Best practice for Rust coding. Always activate this skill before authoring Rust code or answering questions about Rust.

Important dos and don'ts for working with Rust source code

Use cargo add to add new dependencies or features rather than editing Cargo.toml directly
Before finishing your turn, when editing Rust code:
- Run cargo fmt after modifying Rust source files to ensure consistent formatting
- Run tests (most commonly cargo test --all --workspace, though some projects may have other commands)

Trustgrade A

passBody integrity
Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.
passType matchnot applicable to this artifact type
Whether the artifact is really the kind of thing its metadata claims it is.
passFreshness
How long since the source repository was last pushed to.
passPrompt injection
Scans the artifact's own text for instructions aimed at your agent rather than at you.
passLicense
Whether the source repository declares an SPDX license permissive enough to redistribute.

How the grade is calculated

Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:

Aevery check passed
Bone warning
Ctwo warnings
Dprompt injection or body integrity failed, or three warnings
Fone of those failed, and something else is wrong

These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.

Versions

git-cd43816641612026-07-31