CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

rust-patterns

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

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.kiro/skills/rust-patterns/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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, actionability-focused Rust idiom catalog with concrete Good/Bad code examples and useful tooling commands. Its main weaknesses are token weight (much of it duplicates standard Rust knowledge Claude already has) and the total absence of progressive disclosure — a ~500-line single file where reference material should be split out.

Suggestions

Split the SKILL.md into an overview plus one-level-deep reference files (e.g. references/error-handling.md, references/concurrency.md, references/tooling.md, references/crate-structure.md) and link them explicitly, keeping only the principle summaries and a few exemplar patterns inline.

Cut sections that restate knowledge Claude already has (borrow-vs-clone basics, Option combinator chains, iterator-vs-loop, Arc<Mutex> mechanics) and keep only project-specific conventions or non-obvious guidance, trimming toward the lean '## Extract PDF text' style of the anchor-5 example.

Fix code correctness gaps: the async example chains '.context("request failed")' on a plain Response after the first '?' (won't compile), and several snippets depend on undefined types — make examples self-contained and copy-paste runnable.

DimensionReasoningScore

Conciseness

The body is mostly efficient in form — minimal prose, compact Good/Bad code pairs — but much of it restates knowledge Claude already has (borrow-don't-clone, '?' over 'unwrap()', iterator chains over loops, Arc<Mutex> basics), and the 500-line volume could be tightened considerably. Not 4 because several sections add little beyond standard Rust competence; not 2 because there is no padded prose or conceptual explanation (e.g., no 'what is ownership' tutorial text).

3 / 5

Actionability

Nearly all guidance is concrete, executable Rust plus specific cargo commands (clippy, fmt, test, audit). Not 5 because some snippets are illustrative rather than copy-paste ready (undefined User/Config/connect() items) and the async example chains '.context()' on a non-Result value after the first '?', which would not compile; not 3 because the guidance is real executable code, not pseudocode.

4 / 5

Workflow Clarity

This is a pattern-reference skill, not a multi-step workflow; the 'When to Use' section plus the 'How It Works' six-area map make application unambiguous, and there are no destructive or batch operations that would demand validation checkpoints. Not 5 because there is no process guidance for applying the patterns in a review/refactor loop (e.g., 'run clippy, fix lints, re-run'), which would fit the stated use cases.

4 / 5

Progressive Disclosure

Section structure is clear and well-organized, but the skill is a ~500-line monolith with all reference material inlined — the crate-layout tree, the cargo tooling catalog, and the idiom tables belong in one-level-deep reference files, and no bundle files exist. Not 2 because, unlike anchor 2's header-less inline dump, the content has clear sections and navigation; not 4 because nothing is split out and the whole catalog loads into context on every trigger — the under-50-line exception does not apply at this length.

3 / 5

Total

14

/

20

Passed

Description

65%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 is distinct and on-domain, with good natural trigger keywords for Rust work. Its main weaknesses are the absence of any 'Use when...' trigger clause (capping completeness at 3) and the lack of concrete action verbs — it enumerates topic areas rather than capabilities.

Suggestions

Add an explicit trigger clause, e.g. 'Use when writing, reviewing, or refactoring Rust code, or when the user mentions Rust, the borrow checker, or Cargo.'

Convert topic nouns into concrete actions — e.g. 'Apply idiomatic ownership and borrowing, propagate errors with Result and ?, model states as enums...' — so capabilities read as verbs rather than a topic list.

Include natural synonyms users actually say ('borrow checker', 'lifetimes', 'async/tokio', 'Cargo') to strengthen trigger-term coverage.

DimensionReasoningScore

Specificity

The description names the Rust domain and several concrete topic areas ("ownership, error handling, traits, concurrency"), but lists no actions or verbs — it is a topic catalog rather than a list of specific capabilities. Not 4 because anchor 4 requires 'several specific actions', which are absent; not 2 because the topics named are concrete and broader than a single generic action.

3 / 5

Completeness

Has a clear 'what' ("Idiomatic Rust patterns, ownership, error handling, traits, concurrency... safe, performant applications") but no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 3 per the rubric guidelines. Not 4 because the 'when' is entirely absent rather than merely implicit-and-improvable — the cap is explicit.

3 / 5

Trigger Term Quality

Good natural keyword coverage: "Rust", "ownership", "error handling", "traits", "concurrency", "best practices" are terms users would naturally say. Not 5 because common synonyms users actually use are missing — 'borrow checker', 'lifetimes', 'async', 'Cargo'; not 3 because coverage goes beyond 'some relevant keywords'.

4 / 5

Distinctiveness Conflict Risk

Clear niche with distinct triggers: 'Rust', 'ownership', 'traits', and 'concurrency' in this combination point unambiguously to Rust development, with minimal overlap risk against other skills. Not 4 because there is no closely related skill category it would falsely trigger for.

5 / 5

Total

15

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

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

Reviewed

Table of Contents

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.