CtrlK
BlogDocsLog inGet started
Tessl Logo

rust-systems

Rust systems programming patterns including ownership, traits, async runtime, error handling, and unsafe guidelines

64

Quality

76%

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 ./skills/rust-systems/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

80%

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

The body is token-efficient and highly actionable with concrete Rust examples and a useful anti-patterns/checklist section, but it is a monolithic reference catalog with no progressive disclosure or explicit workflow validation loop. Splitting heavier sections into reference files and reconciling the async example's use of .unwrap() with its own anti-pattern list would improve it.

Suggestions

Move the larger code sections (traits/generics, async patterns, builder) into reference files (e.g., ASYNC.md, TRAITS.md) with one-level-deep links so SKILL.md stays an overview.

Fix the internal contradiction: the async example calls .unwrap() on the semaphore permit and .expect() on ctrl_c while the Anti-Patterns section forbids .unwrap()/.expect() in library code.

Add a brief validate->fix->retry note for risky items (e.g., unsafe blocks) so the checklist doubles as an explicit workflow checkpoint rather than a flat list.

DimensionReasoningScore

Conciseness

The body is lean: each section is real code followed by a one-line rule ('Prefer borrowing over ownership transfer. Use Clone only when necessary.'), with no padding explaining what Rust is or how libraries work, so every token earns its place.

3 / 3

Actionability

Concrete, idiomatic, copy-paste-ready Rust examples span thiserror enums, trait repositories, semaphore-bounded async, and a builder, giving fully executable guidance rather than vague direction.

3 / 3

Workflow Clarity

There is no multi-step process sequenced with validation checkpoints; the closing Checklist acts as a verification list but the skill is a reference catalog, matching 'steps listed but validation gaps' rather than a full validate->fix->retry workflow.

2 / 3

Progressive Disclosure

Content is well-organized into clear section headers but all ~185 lines live inline in a single SKILL.md with no one-level-deep references to split out the larger code sections, matching 'some structure but content that should be separate is inline'.

2 / 3

Total

10

/

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 specific and distinctive with strong natural trigger terms for the Rust domain, but it lacks an explicit 'when to use' trigger clause, which caps its completeness. Adding a 'Use when...' sentence would raise the completeness and trigger guidance.

Suggestions

Add an explicit trigger clause such as 'Use when writing or reviewing Rust systems code involving ownership, traits, async, error handling, or unsafe blocks.'

Reframe the listed topics as concrete actions (e.g., 'Apply ownership and borrowing patterns, define trait-based abstractions, structure async concurrency') to lift specificity from coverage areas to actions.

DimensionReasoningScore

Specificity

The description names the domain ('Rust systems programming patterns') and lists five concrete subtopics ('ownership, traits, async runtime, error handling, and unsafe guidelines'), but these are coverage areas rather than concrete actions a user would invoke, matching the 'names domain and some actions, but not comprehensive' anchor rather than the 'lists multiple specific concrete actions' anchor.

2 / 3

Completeness

It states what the skill covers but provides no 'Use when...' clause or equivalent trigger guidance, so per the judging guideline completeness is capped at 2 ('has what, but when is missing or only implied').

2 / 3

Trigger Term Quality

Terms like 'ownership', 'traits', 'async', 'error handling', and 'unsafe' are exactly what Rust users naturally say when they need these patterns, giving good coverage of natural trigger keywords.

3 / 3

Distinctiveness Conflict Risk

'Rust systems programming' is a clear, narrow niche with distinct terminology, making it unlikely to trigger for unrelated skills.

3 / 3

Total

10

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
rohitg00/awesome-claude-code-toolkit
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.