rust-patterns

Idiomatic Rust patterns, ownership, error handling, traits, concurrency, and best practices for building safe, performant applications.

Quality

68%

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 ./.kiro/skills/rust-patterns/SKILL.md

Quality

Content

65%

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

The skill is highly actionable with comprehensive executable Rust examples, but it is a long monolithic file with repeated themes, no external reference split, and no sequenced workflow with validation checkpoints.

Suggestions

Split the quick-reference table, anti-patterns, and tooling command catalog into separate referenced files (e.g. REFERENCE.md, ANTI_PATTERNS.md) to enable progressive disclosure.

Consolidate the repeated unwrap/clone guidance so each idiom appears once and cross-references rather than restating across sections.

Add a brief 'Workflow' section sequencing how to apply the patterns when reviewing or refactoring code, with a validation checkpoint (e.g. run cargo clippy + cargo test before declaring done).

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and assumes Claude's competence (no beginner explanations), but at ~500 lines it is encyclopedic and repeats themes (e.g. unwrap avoidance appears in Error Handling, Quick Reference, and Anti-Patterns), so it could be tightened.	2 / 3
Actionability	It provides abundant copy-paste-ready, executable Rust code and concrete cargo commands across every section, fully meeting the 'executable, specific examples' anchor.	3 / 3
Workflow Clarity	As a patterns/reference skill it has no multi-step process to sequence; the 'When to Use' list gives triggers but there are no validation checkpoints or feedback loops, so it sits at the 'sequence present but checkpoints missing' level.	2 / 3
Progressive Disclosure	No bundle files exist and all content is inlined into a single ~500-line file; material such as the quick-reference table, anti-patterns, and tooling commands that could be split into referenced files is instead monolithic.	2 / 3
	Total	9 / 12 Passed

Description

72%

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 is distinctive and uses natural Rust-domain trigger terms, but it omits any explicit 'when to use' guidance and lists topics rather than concrete actions, capping completeness and specificity at 2.

Suggestions

Append an explicit trigger clause, e.g. 'Use when writing, reviewing, or refactoring Rust code or designing crate/module structure.'

Reframe topic labels as concrete actions (e.g. 'enforce ownership rules, propagate errors with Result/?, model states as enums') to lift specificity.

Add common natural variants users might say ('Rust', 'Rust idioms', 'borrow checker', 'lifetimes') to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the domain and several topic areas ('ownership, error handling, traits, concurrency') but these are subject labels rather than concrete actions with verbs, matching the 'names domain and some actions' anchor.	2 / 3
Completeness	It clearly states what the skill covers but provides no 'Use when...' clause or equivalent explicit trigger guidance, so per the judging guidelines completeness is capped at 2.	2 / 3
Trigger Term Quality	Terms like 'Rust patterns', 'ownership', 'error handling', 'traits', and 'concurrency' are exactly the natural language a Rust developer would invoke, giving good coverage of likely user phrasing.	3 / 3
Distinctiveness Conflict Risk	The description is squarely Rust-specific ('Idiomatic Rust patterns'), carving a clear niche unlikely to fire for non-Rust skills.	3 / 3
	Total	10 / 12 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: .kiro/skills/rust-patterns/SKILL.md
Commit: 0c1d7be

Reviewed: about 10 hours 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.