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.
89
92%
Does it follow best practices?
Impact
85%
1.06xAverage score across 6 eval scenarios
Passed
No known issues
Quality
Discovery
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 thoroughly covers Rust-specific capabilities with concrete actions, explicit trigger guidance, and highly distinctive domain terminology. It follows the recommended pattern of 'what it does' + 'Use when' + trigger keywords, making it easy for Claude to select appropriately. The description is comprehensive without being padded, and 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, ownership issues, trait APIs, async concurrency, FFI, performance optimization). Also includes an 'Invoke for' keyword list. | 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. Very unlikely to conflict with non-Rust skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured Rust skill with excellent actionability through executable code examples and strong progressive disclosure via the reference table. The main weaknesses are minor conciseness issues: the persona description, some obvious constraints (things Claude already knows about Rust best practices), and the keyword-dump Knowledge Reference section add tokens without proportional value. Overall it's a solid, practical skill file.
Suggestions
Remove the persona sentence at the top and the 'Knowledge Reference' keyword list at the bottom — neither adds actionable guidance.
Trim the MUST DO/MUST NOT DO lists to only non-obvious constraints; items like 'Use ownership and borrowing for memory safety' are fundamental Rust knowledge Claude already has.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but includes some unnecessary framing ('Senior Rust engineer with deep expertise...') and the Knowledge Reference section at the bottom is just a keyword list that adds no actionable value. The MUST DO/MUST NOT DO lists contain items Claude already knows (e.g., 'Use ownership and borrowing for memory safety'). However, the code examples are tight and the reference table is well-structured. | 2 / 3 |
Actionability | All code examples are fully executable, copy-paste ready Rust code covering key patterns (lifetimes, traits, error handling, async). Validation commands are concrete and specific. The output template gives a clear deliverable structure. | 3 / 3 |
Workflow Clarity | The core workflow is clearly sequenced with an explicit validation step (step 5) that includes specific commands and a 'fix all warnings before finalising' checkpoint. The validation commands section reinforces this with concrete bash commands. The workflow covers the full cycle from design through validation. | 3 / 3 |
Progressive Disclosure | Excellent use of a reference table with clear 'Load When' conditions pointing to one-level-deep reference files. The main skill provides a concise overview with key examples inline while deferring detailed guidance to topic-specific reference files. Navigation is intuitive. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%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
3d95bb1
- Reviewed
Table of Contents
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.