rust

Rust coding best practices for idiomatic, efficient, and maintainable code. Use when writing Rust code, reviewing code, or learning Rust patterns.

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

92%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A tight, highly actionable reference of Rust best practices with concrete BAD/GOOD code and an explicit quality-gate sequence. Its only structural weakness is monolithic length with no progressive disclosure splitting the catalog into reference files.

Suggestions

Split the larger catalogs (Ownership & Borrowing, API Design, Async, Performance) into a references/ file (e.g. PATTERNS.md) and keep SKILL.md as a concise overview with one-level-deep links, raising progressive_disclosure toward 3.

Add a short ordering note near the top or the Quick Reference stating the quality gate is run after applying a change, making the validation feedback loop explicit rather than implied by a single chained command.

Dimension	Reasoning	Score
Conciseness	Lean and example-driven throughout: short headers followed by BAD/GOOD code with no padding explaining Rust concepts or the borrow checker, assuming Claude's competence and earning every token, matching the anchor-3 'lean and efficient' example.	3 / 3
Actionability	Nearly all guidance is executable Rust or specific commands (cargo fmt/clippy/test, Vec::with_capacity, tokio::spawn_blocking) with copy-paste-ready BAD/GOOD pairs; the few '{ ... }' signature stubs illustrate signatures rather than logic, keeping it at anchor 3.	3 / 3
Workflow Clarity	A reference/catalog skill rather than a multi-step process, and per the rubric's simple-skill note it scores 3 when the single action is unambiguous; the Quick Reference provides an explicit quality-gate checkpoint ('cargo fmt -- --check && cargo clippy -- -D warnings && cargo test') with no destructive/batch operations requiring missing feedback loops.	3 / 3
Progressive Disclosure	No bundle files exist, but the ~380-line body is a monolithic catalog with all patterns inline and no overview pointing to one-level-deep reference files; well-organized by headers yet matches anchor-2 where 'content that should be separate is inline' rather than anchor-3's reference-split structure.	2 / 3
	Total	11 / 12 Passed

Description

90%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that clearly states both capability and explicit use-when triggers with natural keyword coverage. The only weakness is specificity: it describes code qualities rather than enumerating concrete actions.

Suggestions

Replace the attribute-based phrasing with a short list of concrete actions, e.g. 'Write idiomatic Rust, handle errors, manage ownership and borrowing, and apply performance and API-design patterns.'

Dimension	Reasoning	Score
Specificity	Names the Rust domain and qualities ('idiomatic, efficient, and maintainable code') but frames the what as attributes rather than listing multiple concrete actions, sitting above the anchor-2 'Processes PDF files and extracts content' yet below the anchor-3 list of specific operations.	2 / 3
Completeness	Explicitly answers both what ('Rust coding best practices for idiomatic, efficient, and maintainable code') and when ('Use when writing Rust code, reviewing code, or learning Rust patterns') with an explicit trigger clause, matching the anchor-3 example.	3 / 3
Trigger Term Quality	'Use when writing Rust code, reviewing code, or learning Rust patterns' gives good coverage of natural terms a user would say (Rust code, reviewing, patterns), matching the anchor-3 example of natural keyword coverage.	3 / 3
Distinctiveness Conflict Risk	Rust-specific niche with distinct triggers ('writing Rust code', 'Rust patterns') makes it unlikely to fire for unrelated skills, matching the anchor-3 'clear niche with distinct triggers'.	3 / 3
	Total	11 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning

	Total	15 / 16 Passed

Repository: pgdogdev/pgdog
Path: .claude/skills/rust/SKILL.md
Commit: c4f63fd

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.