rust-patterns

Idiomatic Rust patterns, ownership, error handling, traits, concurrency, and best practices for building safe, performant applications. Use when writing or reviewing Rust code and ownership, error handling, traits, or concurrency is in question.

Quality

76%

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 ./skills/rust-patterns/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 thorough, well-organized idiomatic-Rust reference with strong executable examples and good/bad comparisons. Its main weakness is the absence of progressive disclosure: a large monolithic file with no bundle references, and no multi-step workflow with validation checkpoints (though the latter is less critical for a patterns reference).

Suggestions

Split detailed code galleries (e.g. the per-pattern examples) into reference files under references/ and link to them one level deep, leaving SKILL.md as a concise overview to improve progressive_disclosure.

Tighten or remove concept restatements Claude already knows (e.g. the ownership intro sentence and the closing 'Remember' line) to lift conciseness toward 5.

Replace todo!() placeholders and implicit context (the Command enum) with self-contained, runnable snippets to push actionability to 5.

Dimension	Reasoning	Score
Conciseness	Mostly lean and code-forward, assuming Rust competence, with only minor over-explanation (e.g. 'Rust's ownership system prevents data races... at compile time' restates a basic concept and the closing 'Remember' line is light padding); not a 5 because of those small trimmable passages.	4 / 5
Actionability	Extensive copy-paste-ready, executable code with good/bad pairs, concrete cargo commands, and a quick-reference table; not a 5 because a few examples use todo!() placeholders or assume undefined context (e.g. the Command enum).	4 / 5
Workflow Clarity	Content is organized as topical reference sections rather than a sequenced multi-step process, so checkpoints and validation feedback loops are absent; this is appropriate for a patterns reference but lands at the 'sequence present but checkpoints missing' level rather than a higher workflow score.	3 / 5
Progressive Disclosure	No bundle files exist and all ~500 lines of content live inline in one monolithic file with clear headers but no one-level-deep references; matches the 'some structure, content that should be separate is inline' anchor rather than a 4 because nothing is split into referenced files.	3 / 5
	Total	14 / 20 Passed

Description

87%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.

A strong, well-scoped description that clearly states both capabilities and explicit 'Use when' trigger guidance for the Rust domain. Minor room to improve via more action-verb framing and additional natural synonyms like 'borrow checker' or 'lifetimes'.

Dimension	Reasoning	Score
Specificity	Names the Rust domain plus several concrete sub-areas (ownership, error handling, traits, concurrency) and outcomes (safe, performant applications), matching the 'lists several specific actions; minor gaps' anchor; not a 5 because capabilities are framed as topics/patterns rather than discrete concrete actions.	4 / 5
Completeness	Explicitly answers both what ('Idiomatic Rust patterns, ownership, error handling, traits, concurrency, and best practices') and when ('Use when writing or reviewing Rust code and ownership, error handling, traits, or concurrency is in question') with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Includes natural phrases a Rust user would actually say ('writing or reviewing Rust code', 'ownership, error handling, traits, or concurrency'), giving good keyword coverage; not a 5 because some common synonyms/extensions (e.g. 'borrow checker', 'lifetimes', file extensions) are absent.	4 / 5
Distinctiveness Conflict Risk	Scoped to a clear Rust-specific niche with distinct triggers (Rust code, ownership, traits, concurrency), giving minimal conflict risk with other language skills.	5 / 5
	Total	18 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (501 lines); consider splitting into references/ and linking	Warning
metadata_version	'metadata.version' is missing	Warning

	Total	14 / 16 Passed

Repository: affaan-m/ECC
Path: skills/rust-patterns/SKILL.md
Commit: e04ea0b

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