rust-engineer

Writes, reviews, and debugs idiomatic Rust code with memory safety and zero-cost abstractions. Implements ownership patterns, manages lifetimes, designs trait hierarchies, builds async applications with tokio, and structures error handling with Result/Option. Use when building Rust applications, solving ownership or borrowing issues, designing trait-based APIs, implementing async/await concurrency, creating FFI bindings, or optimizing for performance and memory safety. Invoke for Rust, Cargo, ownership, borrowing, lifetimes, async Rust, tokio, zero-cost abstractions, memory safety, systems programming.

Quality

88%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

77%

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, well-structured Rust skill with excellent actionability through complete, executable code examples and clear workflow sequencing with validation checkpoints. Its main weaknesses are moderate verbosity (persona description, knowledge reference section listing things Claude knows, and some redundant best-practice reminders) and the absence of the referenced bundle files that the progressive disclosure table points to.

Suggestions

Remove the persona description opening paragraph and the 'Knowledge Reference' section — Claude already knows these concepts and they consume tokens without adding value.

Provide the referenced files (references/ownership.md, references/traits.md, etc.) or remove the reference table if they don't exist, as broken references reduce trust in the skill.

Trim the MUST DO/MUST NOT DO lists to only non-obvious constraints — items like 'handle all errors explicitly' and 'use cargo fmt' are standard Rust practice that Claude already knows.

Dimension	Reasoning	Score
Conciseness	The skill is mostly efficient with good code examples, but includes some unnecessary content like the persona description ('Senior Rust engineer with deep expertise...'), the 'Knowledge Reference' section listing things Claude already knows, and the output templates section which is somewhat generic. The MUST DO/MUST NOT DO lists contain items that are standard Rust best practices Claude would already know.	2 / 3
Actionability	All code examples are fully executable and copy-paste ready — lifetime annotations, trait implementations, thiserror usage, async/tokio patterns, and validation commands are all concrete and complete. The validation commands section provides exact CLI invocations.	3 / 3
Workflow Clarity	The core workflow provides a clear 5-step sequence with an explicit validation checkpoint (step 5) that includes specific commands. The validation step explicitly states 'fix all warnings before finalising,' creating a feedback loop. The validation commands section reinforces this with exact commands.	3 / 3
Progressive Disclosure	The reference table with 5 topic-specific files is well-structured with clear 'Load When' triggers, which is excellent design. However, no bundle files are provided, meaning all referenced files (references/ownership.md, references/traits.md, etc.) are missing. The inline content is also fairly extensive — the key patterns section could arguably live in the referenced files rather than being duplicated in the main skill.	2 / 3
	Total	10 / 12 Passed

Description

100%

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 strong skill description that excels across all dimensions. It provides specific concrete actions, comprehensive trigger terms that Rust developers would naturally use, explicit 'Use when' guidance, and highly distinctive Rust-specific terminology that minimizes conflict risk with other skills. The description uses proper third-person voice throughout.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: writes/reviews/debugs Rust code, implements ownership patterns, manages lifetimes, designs trait hierarchies, builds async applications with tokio, structures error handling with Result/Option.	3 / 3
Completeness	Clearly answers both 'what' (writes, reviews, debugs Rust code with specific patterns) and 'when' (explicit 'Use when' clause covering building Rust apps, solving ownership issues, designing trait APIs, async concurrency, FFI bindings, performance optimization).	3 / 3
Trigger Term Quality	Excellent coverage of natural terms users would say: Rust, Cargo, ownership, borrowing, lifetimes, async Rust, tokio, zero-cost abstractions, memory safety, systems programming, FFI bindings, trait-based APIs. These are terms Rust developers naturally use.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive with Rust-specific terminology (ownership, borrowing, lifetimes, tokio, Cargo, zero-cost abstractions) that clearly separates it from general programming or other language-specific skills.	3 / 3
	Total	12 / 12 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: Jeffallan/claude-skills
Commit: e8be415

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