Name: rust-pro
Rating: 45.6 (1 reviews)
Author: administrakt0r

Blog Docs Log in Get started

rust-pro

Master Rust 1.75+ with modern async patterns, advanced type system features, and production-ready systems programming.

Quality

48%

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/AI-Agents-Safe-Coding-Skills-claude/skills/rust-pro/SKILL.md

The canonical home for this skill is rust-pro in administrakt0r/AI-Agents-Safe-Coding-Skills

Quality

Content

35%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 content is a verbose capability catalog restating Rust knowledge Claude already has, with abstract instructions and no executable code or validation checkpoints. It needs concrete examples, tightened prose, and reference files for the long capability lists.

Suggestions

Replace the enumerated capability lists with concise, executable guidance and code snippets for the most common tasks (async service setup, lifetime fixes, profiling commands).

Move the detailed capability inventories into reference files (e.g. references/capabilities.md, references/async-patterns.md) and keep SKILL.md as a lean overview with one-level-deep links, raising progressive_disclosure.

Add explicit validation/checkpoint steps to the workflow (e.g. 'run cargo test && cargo clippy before considering optimization') to improve workflow_clarity.

Dimension	Reasoning	Score
Conciseness	The body is ~170 lines of capability bullet lists that extensively enumerate Rust concepts Claude already knows ('Rc, Arc, and weak references', 'GATs', 'Tokio ecosystem: axum, tower, hyper'), which the rubric penalizes; it is noticeably verbose with padded sections restating known knowledge.	2 / 5
Actionability	Guidance is abstract ('Choose async/runtime and crate ecosystem approach', 'Implement with tests and linting', 'Design type-safe APIs') with no concrete code, commands, crate names per task, or executable examples — only high-level hints missing the specific steps to execute.	2 / 5
Workflow Clarity	A rough sequence exists ('Instructions' 4 steps and 'Response Approach' 8 steps), but there are no validation checkpoints or feedback loops; the skill is not destructive/batch so no hard cap applies, fitting anchor 3 (steps listed but checkpoints missing).	3 / 5
Progressive Disclosure	No bundle files exist (references/scripts/assets absent), so the single SKILL.md inlines long capability lists that belong in separate reference files; section structure is present but content is not split and references are absent, matching anchor 3.	3 / 5
	Total	10 / 20 Passed

Description

61%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 clearly names a distinct Rust 1.75+ niche with several feature areas, but lacks an explicit 'Use when...' trigger clause and enumerates feature areas rather than concrete actions. Adding trigger phrases would raise completeness and trigger-term quality.

Suggestions

Add an explicit 'Use when...' clause naming concrete triggers, e.g. 'Use when building Rust services, solving ownership/lifetime or async issues, or optimizing memory-safe performance.'

Reframe capability areas as concrete actions (e.g. 'design async services, navigate lifetime/trait constraints, optimize hotspots') to push specificity toward 4-5.

Include more natural synonyms users say ('Tokio', 'lifetimes', 'cargo', 'axum') to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the Rust 1.75+ domain plus several concrete feature areas ('modern async patterns, advanced type system features, production-ready systems programming'), but the 'Master...with...' framing lists feature areas rather than concrete actions, so it sits between anchor 3 and 4 — closer to 3 since actions are not enumerated comprehensively.	3 / 5
Completeness	Has a clear 'what' ('Master Rust 1.75+ with modern async patterns...') but no 'when'/'Use when...' clause; per guideline a missing explicit trigger clause caps completeness at 3.	3 / 5
Trigger Term Quality	Includes natural terms a user would say ('Rust', 'async', 'systems programming') with good coverage, but misses common synonyms/variations like 'lifetimes', 'Tokio', 'cargo', or 'Rust services' that users frequently mention.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche (Rust 1.75+ advanced/systems) that is distinguishable from generic language skills, with only minor overlap risk against a broad coding skill.	4 / 5
	Total	14 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/rust-pro/SKILL.md
Commit: 57c135b

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