CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

rust-async-patterns

Master Rust async programming with Tokio, async traits, error handling, and concurrent patterns. Use when building async Rust applications, implementing concurrent systems, or debugging async code.

Quality

77%

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

Quality

Content

61%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-structured skill body with an executable quick start, concrete best practices, and a proper one-level-deep reference split. Its main weaknesses are the Core Concepts section padding tokens with async fundamentals Claude already knows and the absence of any sequenced workflow for approaching async development or debugging.

Suggestions

Remove or relocate the 'Core Concepts' section (the Future/Waker diagram and the abstraction definitions table) to references/details.md — this is foundational knowledge Claude already has and costs context tokens on every load.

Add a short sequenced workflow (e.g., for debugging an async issue: reproduce with tracing instrumentation -> check for blocking calls/lock-across-await -> isolate with #[tokio::main(flavor = ...)] or tokio-console) so the skill guides a process rather than only listing patterns.

In the details.md pointer, briefly enumerate the pattern categories (tasks, channels, error handling, graceful shutdown, async traits, streams, resource management, debugging tips) so navigation to the reference tier is self-describing.

DimensionReasoningScore

Conciseness

The Quick Start, reference pointer, and Best Practices sections are tight, but the 'Core Concepts' section pads the file with material Claude already knows — a Future/Waker polling diagram and a table defining 'Future: Lazy computation that may complete later', 'await: Suspend until future completes', and 'Task: Spawned future running concurrently'. This is 'mostly efficient but includes some unnecessary explanation' rather than level 2, since the padding is confined to one section.

3 / 5

Actionability

The Quick Start provides an executable Cargo.toml and a complete, runnable #[tokio::main] example, and the Best Practices cite concrete APIs (tokio::select!, JoinSet, CancellationToken, semaphores). It falls short of level 5 because the details.md patterns are not surfaced inline for even the most common cases and some do's/don'ts ('Handle cancellation - Check CancellationToken') are hints rather than copy-paste guidance.

4 / 5

Workflow Clarity

The body is organized as reference material (when-to-use list, concepts, quick start, best practices) rather than a sequenced process — there is no explicit order of attack for building or debugging an async system. It is not below 3 because the material is coherent and requires no validation checkpoints (no destructive or batch operations), but it lacks the sequence and checkpoints of level 4.

3 / 5

Progressive Disclosure

The bundle structure is sound: a lean SKILL.md overview pointing one level deep to a real, substantive references/details.md, clearly signaled ('Detailed pattern documentation lives in references/details.md. Read that file when the navigation tier above is insufficient'). Not level 5 because the foundational Core Concepts material inlined in SKILL.md arguably belongs in the reference tier, and the pointer could enumerate what details.md covers to aid navigation.

4 / 5

Total

14

/

20

Passed

Description

83%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 description with an explicit 'Use when...' clause, concrete technical scope, and natural trigger terms. It clearly and explicitly answers both what the skill does and when to use it, with only minor gaps in keyword synonyms and slight overlap risk with general Rust skills.

DimensionReasoningScore

Specificity

The description names the domain (Rust async) and several concrete areas — 'Tokio, async traits, error handling, and concurrent patterns' — giving specific technical scope with only minor gaps (e.g., streams/channels are covered in the body but not mentioned). It lists topics rather than fully enumerated actions, so it sits at 'several specific actions; minor gaps in coverage' rather than the comprehensive level 5.

4 / 5

Completeness

It explicitly answers both questions: 'what' via 'Master Rust async programming with Tokio, async traits, error handling, and concurrent patterns' and 'when' via a concrete 'Use when...' clause with three distinct trigger scenarios. Not below 5 because both halves are explicit and specific.

5 / 5

Trigger Term Quality

Natural trigger phrases like 'building async Rust applications', 'implementing concurrent systems', and 'debugging async code' match what users would actually say. Common variations such as 'async/await', 'futures', 'tokio tasks', or '.rs' are absent, so it falls just short of comprehensive keyword coverage.

4 / 5

Distinctiveness Conflict Risk

The async-Rust-with-Tokio niche is well-delineated and unlikely to trigger for unrelated skills, but phrases like 'error handling' and 'debugging async code' have minor overlap with general Rust, debugging, or error-handling skills — matching 'mostly distinct; minor overlap risk with closely related skills' rather than the minimal-conflict level 5.

4 / 5

Total

17

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

wshobson/agents

Path

plugins/systems-programming/skills/rust-async-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.