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

74%

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

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-organized overview with executable Quick Start code and a real one-level-deep reference file. It is held back by restating basic async concepts Claude already knows and lacking explicit workflow checkpoints.

Suggestions

Trim or remove the Core Concepts table and async execution diagram, which restate basic knowledge Claude already has about Future/await/Task/Runtime.

Make the reference pointer a descriptive markdown link (e.g., 'See [details.md](references/details.md) for JoinSet, select!, and channel patterns') so the destination's contents are clear.

Add a short sequenced workflow for the most common task (e.g., pick runtime → spawn tasks → wire channels → handle errors) with an explicit validation/checkpoint step.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete Quick Start code, but the Core Concepts table explaining Future/async fn/await/Task/Runtime and the async execution diagram restate basic concepts Claude already knows, adding unnecessary tokens.	3 / 5
Actionability	Quick Start provides copy-paste-ready Cargo.toml and Rust code, and Best Practices give concrete directives (tokio::select!, JoinSet, CancellationToken); minor gaps as deeper examples are delegated to references.	4 / 5
Workflow Clarity	A loose navigation sequence exists (When to Use → Core Concepts → Quick Start → details → Best Practices) but there is no multi-step process with explicit checkpoints or validation; acceptable for a patterns skill but not a clearly sequenced workflow.	3 / 5
Progressive Disclosure	The body is a clear overview that signals a one-level-deep reference ('Detailed pattern documentation lives in references/details.md') and the referenced file exists; minor gap in that the pointer uses an inline code path rather than a descriptive markdown link.	4 / 5
	Total	14 / 20 Passed

Description

87%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 that clearly states the domain and capabilities with an explicit 'Use when' trigger clause covering several natural scenarios. Minor room for improvement in adding synonyms and more discrete action verbs.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete sub-areas ('Tokio, async traits, error handling, and concurrent patterns'), analogous to listing several specific capabilities; gaps are minor as these are topic areas rather than discrete actions.	4 / 5
Completeness	Explicitly answers both what ('Master Rust async programming with Tokio, async traits, error handling, and concurrent patterns') and when ('Use when building async Rust applications, implementing concurrent systems, or debugging async code') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural trigger phrases like 'building async Rust applications', 'implementing concurrent systems', and 'debugging async code' cover what users would say, but a few common synonyms (e.g., async I/O, futures, runtime) are missing.	4 / 5
Distinctiveness Conflict Risk	The 'Rust async programming with Tokio' niche is clearly distinct with specific triggers (async Rust, Tokio, concurrent systems), giving minimal conflict risk with other skills.	5 / 5
	Total	18 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: wshobson/agents
Path: plugins/systems-programming/skills/rust-async-patterns/SKILL.md
Commit: d6837ae

Reviewed: about 13 hours 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.