CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

Install with Tessl CLI

npx tessl i github:wshobson/agents --skill rust-async-patterns
What are skills?

81

Quality

77%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/systems-programming/skills/rust-async-patterns/SKILL.md
SKILL.md
Review
Evals

Discovery

89%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a solid skill description with explicit 'Use when' guidance and good trigger term coverage for the Rust async ecosystem. The main weakness is that capabilities are described as topic areas rather than concrete actions, making it slightly less actionable than ideal.

Suggestions

Replace topic areas with concrete actions, e.g., 'Implement async functions with Tokio runtime, handle errors in async contexts, debug deadlocks and race conditions' instead of 'Master Rust async programming with Tokio, async traits, error handling'

DimensionReasoningScore

Specificity

Names the domain (Rust async programming) and lists some areas (Tokio, async traits, error handling, concurrent patterns), but these are topic areas rather than concrete actions like 'implement async functions' or 'debug deadlocks'.

2 / 3

Completeness

Clearly answers both what (Master Rust async programming with Tokio, async traits, error handling, concurrent patterns) and when (Use when building async Rust applications, implementing concurrent systems, or debugging async code) with explicit trigger guidance.

3 / 3

Trigger Term Quality

Good coverage of natural terms users would say: 'async', 'Rust', 'Tokio', 'concurrent', 'async code', 'async applications'. These are terms developers naturally use when seeking help with async Rust.

3 / 3

Distinctiveness Conflict Risk

Clear niche targeting specifically Rust async/Tokio programming. The combination of 'Rust', 'async', and 'Tokio' creates a distinct trigger profile unlikely to conflict with general Rust skills or async skills in other languages.

3 / 3

Total

11

/

12

Passed

Implementation

64%

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

This is a solid, actionable skill with excellent executable code examples covering key async Rust patterns. However, it's overly long for a SKILL.md file, includes some explanatory content Claude doesn't need (core concepts table), and lacks explicit validation/verification steps in workflows involving resource management and shutdown sequences.

Suggestions

Remove the 'Core Concepts' section explaining Future/async fn/await - Claude knows these fundamentals

Add explicit validation steps to patterns: verify graceful shutdown completed, check connection pool health, validate task completion

Split into multiple files: keep Quick Start and Pattern 1-2 in SKILL.md, move advanced patterns (streams, resource management, async traits) to separate reference files with clear links

Remove or condense the 'When to Use This Skill' section - this duplicates the skill description

DimensionReasoningScore

Conciseness

The skill is reasonably efficient but includes some unnecessary explanatory content like the 'When to Use This Skill' section and the 'Core Concepts' table explaining what Future/async fn/await are - concepts Claude already knows. The code examples are good but could be tighter.

2 / 3

Actionability

Excellent executable code examples throughout - all patterns include complete, copy-paste ready Rust code with proper imports, error handling, and realistic usage. The Quick Start section provides a working Cargo.toml and main function.

3 / 3

Workflow Clarity

The patterns are well-organized but lack explicit validation checkpoints. For example, the graceful shutdown pattern doesn't verify tasks actually completed, and the resource management patterns don't include validation steps for connection pool health or deadlock detection.

2 / 3

Progressive Disclosure

Content is well-structured with clear sections, but it's a monolithic 400+ line file with no references to external files for advanced topics. The async traits, streams, and resource management sections could be split into separate reference files with links from the main skill.

2 / 3

Total

9

/

12

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (514 lines); consider splitting into references/ and linking

Warning

Total

10

/

11

Passed

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.