rust-pro

Master modern Rust (2024 edition) with async patterns, advanced type system features, and production-ready systems programming. Expert in the current Rust ecosystem including Tokio, axum, and modern crates. Use PROACTIVELY for Rust development, performance optimization, or systems programming.

Quality

42%

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 ./.agents/skills/rust-pro/SKILL.md

Quality

Content

10%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 reads as a verbose capability catalog and persona description rather than actionable guidance: no code, no commands, no validation checkpoints, and no external reference files. It would benefit from drastic condensation plus concrete, executable examples.

Suggestions

Replace the ten capability bullet lists and persona sections with a short overview plus a few executable code/command examples (e.g., a minimal Tokio/axum service, a cargo profile command) so the body actually instructs rather than describes.

Collapse 'Behavioral Traits', 'Knowledge Base', 'Response Approach', and 'Example Interactions' into a brief bullet list or move them to separate reference files linked from the body, cutting the token load substantially.

Add an explicit workflow with validation checkpoints for the risky operations you name (e.g., 'cargo test && cargo clippy' before profiling; re-run benchmarks after any change) to give the sequence real feedback loops.

Dimension	Reasoning	Score
Conciseness	The body is a heavily padded persona listing ten capability categories of ~8 bullets each plus 'Behavioral Traits', 'Knowledge Base', 'Response Approach', and 'Example Interactions', much of it restating concepts Claude already knows ('Ownership rules, borrowing, and move semantics', 'Result and Option patterns'); this matches the severely-verbose, padded anchor and not the merely-noticeable level above.	1 / 5
Actionability	There are no code blocks, commands, or executable examples anywhere in the body; guidance like 'Choose async/runtime and crate ecosystem approach', 'Implement with tests and linting', and 'Profile and optimize hotspots' only describes intent and never instructs concretely, matching the entirely-vague/abstract anchor.	1 / 5
Workflow Clarity	A rough sequence exists (the 4-step 'Instructions' and 8-step 'Response Approach') but steps are high-level with no validation checkpoints, commands, or error-recovery feedback loops; it sits above the incoherent level 1 yet well below a clear sequence with checkpoints, so 2 is the best fit.	2 / 5
Progressive Disclosure	The skill is a single monolithic file with no references/, scripts/, or assets/ bundle present and no signaled links to external material; large blocks that would belong in separate files (capability catalogs, example interactions) are inlined, matching the minimal-structure anchor rather than the no-structure level 1.	2 / 5
	Total	6 / 20 Passed

Description

75%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 well-formed: third-person voice, clear what/when, and concrete ecosystem anchors (Tokio, axum, 2024 edition). It is strong but not perfect, as triggers are slightly generic and a few natural synonyms are absent.

Dimension	Reasoning	Score
Specificity	Names the Rust domain plus several concrete capability areas ('async patterns, advanced type system features, and production-ready systems programming', 'Tokio, axum, and modern crates'); stops short of score 5 because actions are still somewhat abstract rather than the multiple discrete concrete actions the top anchor calls for.	4 / 5
Completeness	Clearly answers 'what' ('Master modern Rust (2024 edition) with async patterns... production-ready systems programming') and 'when' ('Use PROACTIVELY for Rust development, performance optimization, or systems programming'); held at 4 rather than 5 because the 'when' trigger is somewhat generic and could name more concrete scenarios.	4 / 5
Trigger Term Quality	Includes natural trigger terms a user would say ('Rust development', 'performance optimization', 'systems programming', 'Tokio', 'axum'); not a 5 because common synonyms/extensions like '.rs', 'Cargo', or 'Cargo.toml' appear only in when_to_use, not the description itself.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear Rust niche with named ecosystem tools (Tokio, axum), making it distinct from other language skills; minor overlap risk only with a general 'systems programming' skill, keeping it just below a 5.	4 / 5
	Total	16 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: vudovn/ag-kit
Path: .agents/skills/rust-pro/SKILL.md
Commit: 211561c

Reviewed: 8 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.