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

55%

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

Quality

Content

28%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.

The body is a generic template with no substantive Rust async guidance: no code, no concrete patterns, and a referenced playbook file that does not exist on disk. It is lean but content-free, failing to deliver actionable or workflow guidance for the advertised domain.

Suggestions

Replace the boilerplate Instructions with concrete Rust async guidance: executable Tokio snippets for tasks, channels, streams, and error handling.

Either create resources/implementation-playbook.md with the detailed patterns or remove the broken reference, since no bundle file currently exists.

Add a real sequenced workflow with explicit validation checkpoints (e.g., compile/check, runtime test) for concurrent and async operations instead of generic platitudes.

Dimension	Reasoning	Score
Conciseness	The body is short and free of concept over-explanation, but generic boilerplate phrases like 'Apply relevant best practices and validate outcomes' do not earn their place, leaving it mostly efficient with filler that could be tightened.	3 / 5
Actionability	The Instructions are entirely abstract ('Clarify goals', 'Apply relevant best practices', 'Provide actionable steps and verification') with no concrete code, commands, or specific Rust async patterns, matching the score-1 anchor of only describing rather than instructing.	1 / 5
Workflow Clarity	A rough list of platitudes exists in 'Instructions' but there is no real sequenced workflow and no validation checkpoints for risky concurrent/async operations, fitting the score-2 anchor of a rough sequence with poorly defined steps and absent validation.	2 / 5
Progressive Disclosure	The body is sectioned and signals a one-level-deep reference to 'resources/implementation-playbook.md', but no bundle directory exists so the reference is broken, undermining navigation and keeping it at the score-3 level of some structure with organizational gaps.	3 / 5
	Total	9 / 20 Passed

Description

82%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 strong: it clearly states what the skill covers and gives explicit, natural 'Use when' triggers within a well-delineated Rust async niche. Its only weakness is that capabilities are stated as topical areas rather than crisp concrete actions.

Dimension	Reasoning	Score
Specificity	Names the domain ('Rust async programming with Tokio') and several capability areas ('async traits, error handling, and concurrent patterns'), but these are topical areas rather than concrete discrete actions like the score-4 anchor's verb-driven examples, and 'Master ... programming' is generic.	3 / 5
Completeness	It 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, matching the score-5 anchor.	5 / 5
Trigger Term Quality	'Use when building async Rust applications, implementing concurrent systems, or debugging async code' plus 'Tokio' gives good natural keyword coverage users would actually say, though synonyms like 'futures' or 'async/await' are missing.	4 / 5
Distinctiveness Conflict Risk	The Rust + Tokio + async niche is specific with distinct triggers and minimal overlap risk; the only mild breadth is 'concurrent systems', but the overall framing is clearly delineated from other skills.	5 / 5
	Total	17 / 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: rmyndharis/antigravity-skills
Path: skills/rust-async-patterns/SKILL.md
Commit: 3eff4af

Reviewed: 22 days 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.