BD rust-best-practice
Comprehensive, exhaustive reference for idiomatic and production-grade Rust engineering — covers ownership/borrowing/lifetimes, error handling, trait & generic API design, concurrency and async (Tokio), performance and memory layout, unsafe Rust and soundness, testing and property-based testing, Cargo/CI tooling and Clippy lints, web/backend frameworks (Axum/Actix), CLI and systems tools, workspace/project structure, and dependency/supply-chain security. ALWAYS load and consult this skill whenever the word "rust" (or "Rust", "cargo", "crate", ".rs file", "tokio", "actix", "axum", "clippy", "rustc") appears in the conversation, whether the user is writing new Rust code, reviewing/refactoring existing Rust code, debugging a Rust compiler error, designing a Rust API/library/crate, setting up a Rust project or CI pipeline, or asking any question about Rust idioms, ownership, lifetimes, traits, async, unsafe code, performance, or testing. Trigger proactively even for small Rust snippets or one-off questions — do not wait for the user to explicitly ask for "best practices".
Comprehensive, exhaustive reference for idiomatic and production-grade Rust engineering — covers ownership/borrowing/lifetimes, error handling, trait &…
As a process D 49/100 · Unfinished process — weak spots: result and completion, inputs and preconditions, failures and branches
How to improve
- Shorten the description to 1024 characters.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 15. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- error
description-longdescription is 1084 chars, limit 1024
Process rating: all ten parameters 49/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 3 mutating operations with no state check
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 100Steps. 21 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1649 tokens
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 1084: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +5Description quotes 3 example trigger phrases
- +4Structure: 5 headings
- +3Step-by-step instructions: 21 items
- +4Reference files are cited in the instructions (13 of 13)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 61.