rust-patterns

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

Quality

71%

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

72%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 dense, highly actionable Rust patterns reference with strong executable examples and clean Good/Bad contrasts, but it is a long single-file catalog with no progressive disclosure to deeper reference files and no sequenced workflow. Splitting detailed material into referenced files would improve navigation.

Suggestions

Move detailed per-area examples (e.g., full async/concurrency recipes, crate-structure walkthroughs) into reference files linked from a concise overview, improving progressive_disclosure.

Trim the one-line concept restatements and the 'How It Works' paragraph that re-lists the six areas already covered by section headers.

Add a short 'decision workflow' (identify situation -> pick matching pattern -> check Anti-Patterns) to give the catalog an explicit sequenced path.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean Rust snippets with terse Good/Bad commentary and assumes Claude's competence; a few one-line concept restatements ('Rust's ownership system prevents data races...') and the 'How It Works' paragraph re-listing the six areas could be trimmed, so it sits at 4 rather than 5.	4 / 5
Actionability	Abundant executable Rust examples with explicit Good/Bad contrasts plus concrete, copy-paste-ready cargo commands cover the common cases comprehensively.	5 / 5
Workflow Clarity	This is a pattern catalog rather than a sequenced multi-step workflow; section structure exists ('When to Use', 'How It Works', principles) but there is no explicit sequenced workflow with validation checkpoints, so it lands at the midpoint.	3 / 5
Progressive Disclosure	No bundle files exist and roughly 500 lines are inlined in a single SKILL.md despite good section headers; content that could live in separate reference files (detailed per-pattern examples, full crate layout) is all inline, placing it between minimal and good structure.	3 / 5
	Total	15 / 20 Passed

Description

70%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 reasonably specific, well-keyworded Rust-specific description with low conflict risk, but it is missing any explicit 'when to use' trigger guidance, which caps its completeness. Adding a 'Use when...' clause would substantially raise the score.

Suggestions

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

Trim the generic outcome phrasing ('best practices for building safe, performant applications') in favor of one more concrete capability verb.

Include a couple of natural synonyms users might say ('Rust idioms', 'borrow checker', 'lifetimes') to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the Rust domain and several concrete capability areas ('ownership, error handling, traits, concurrency') rather than vague language, though 'best practices' and 'safe, performant applications' are mildly generic outcomes, keeping it just below a 5.	4 / 5
Completeness	The description gives a clear 'what' but contains no 'Use when...' clause or equivalent explicit trigger guidance, so per the rubric cap completeness stays at 3.	3 / 5
Trigger Term Quality	Includes natural Rust terms a user would actually say ('Rust patterns', 'ownership', 'error handling', 'traits', 'concurrency') with good coverage, but misses some common synonyms and phrasings that would push it to 5.	4 / 5
Distinctiveness Conflict Risk	The description is clearly scoped to a Rust-specific niche with distinct triggers and minimal risk of firing for unrelated 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

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

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