rust

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

Quality

69%

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

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/rust/SKILL.md

Quality

Content

65%Weight 40%Scale 1-5

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

A well-organized, actionable Rust best-practices reference with strong code examples and cargo commands. Its main weaknesses are the absence of a real multi-step workflow with validation checkpoints and the lack of progressive disclosure via separate reference files.

Suggestions

Add an explicit validation/feedback loop around the quality gates (e.g., 'If clippy fails, run cargo clippy --fix and re-run') to lift workflow clarity.

Split the large inline reference into one-level-deep files (e.g., references/error-handling.md, references/async.md) and have SKILL.md point to them, improving progressive disclosure.

Complete the placeholder snippets (replace `{ ... }` bodies) or label them as excerpts so examples are unambiguously executable.

Dimension	Reasoning	Score
Conciseness	Mostly lean code-plus-rule reference with little over-explanation of concepts Claude already knows; minor redundancy (e.g., 'Prefer smaller files...' vs 'Refactor large modules...') keeps it just below fully efficient.	4 / 5
Actionability	Abundant BAD/GOOD executable Rust snippets and concrete cargo commands, but several examples use `{ ... }` placeholders rather than being fully copy-paste ready.	4 / 5
Workflow Clarity	This is a patterns reference rather than a multi-step process; the closing quality-gate sequence (fmt, clippy, test) gives a rough order but lacks explicit validation checkpoints and error-recovery feedback loops.	3 / 5
Progressive Disclosure	No bundle files exist and the entire reference is inlined into SKILL.md with good section headers, but at ~385 lines it is a monolithic document with no overview-pointing-to-detail split or one-level-deep references.	3 / 5
	Total	14 / 20 Passed

Description

73%Weight 40%Scale 1-5

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

The description cleanly states a distinct Rust niche and includes an explicit 'Use when...' trigger clause with natural terms. It is strong on distinctiveness and completeness, slightly less concrete on the specific actions it covers.

Suggestions

Replace the abstract attribute list ('idiomatic, efficient, and maintainable code') with a few concrete actions (e.g., 'apply ownership/borrowing patterns, error handling with thiserror, async with tokio') to raise specificity.

Add natural synonyms and file extensions to the trigger clause (e.g., '.rs files', 'cargo', 'crates') for fuller keyword coverage.

Dimension	Reasoning	Score
Specificity	Names the Rust domain and lists a few concrete activities ('writing Rust code, reviewing code, or learning Rust patterns'), but the 'what' leans on attributes ('idiomatic, efficient, and maintainable') rather than multiple specific concrete actions.	3 / 5
Completeness	Both 'what' (Rust coding best practices for idiomatic, efficient, and maintainable code) and an explicit 'when' clause are present, but the 'what' is somewhat abstract compared to a fully concrete action list.	4 / 5
Trigger Term Quality	Natural trigger phrases users would actually say ('writing Rust code, reviewing code, learning Rust patterns') are present, though synonyms like .rs, crates, or cargo are missing.	4 / 5
Distinctiveness Conflict Risk	Rust-specific niche with distinct triggers and minimal overlap risk; unlikely to fire for non-Rust skills.	5 / 5
	Total	16 / 20 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: 7594279

Reviewed: 4 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.