coding-guidelines
Use when asking about Rust code style or best practices. Keywords: naming, formatting, comment, clippy, rustfmt, lint, code style, best practice, P.NAM, G.FMT, code review, naming convention, variable naming, function naming, type naming, 命名规范, 代码风格, 格式化, 最佳实践, 代码审查, 怎么命名
89
87%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
89%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 with excellent trigger term coverage including multilingual keywords and a clear 'Use when' clause. The main weakness is that it relies heavily on keyword listing rather than describing concrete actions the skill performs. Adding 2-3 specific capability statements would improve specificity.
Suggestions
Add concrete action statements like 'Explains Rust naming conventions, configures rustfmt settings, interprets clippy warnings' before the keyword list
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Rust code style/best practices) and mentions some actions implicitly through keywords (naming, formatting, clippy, rustfmt, lint, code review), but doesn't list concrete specific actions like 'enforce naming conventions' or 'run clippy analysis'. | 2 / 3 |
Completeness | Explicitly answers both 'what' (Rust code style/best practices) and 'when' with a clear 'Use when asking about...' clause followed by comprehensive keyword triggers. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms including common variations (naming, formatting, clippy, rustfmt, lint, code style, best practice), specific patterns (P.NAM, G.FMT), granular terms (variable naming, function naming, type naming), and even Chinese equivalents (命名规范, 代码风格, 格式化). | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to Rust-specific code style with distinct triggers like 'clippy', 'rustfmt', and Rust-specific naming convention codes (P.NAM, G.FMT), making it unlikely to conflict with general code style or other language-specific skills. | 3 / 3 |
Total | 11 / 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 an excellent reference-style skill that maximizes information density through effective use of tables. It correctly assumes Claude's baseline Rust knowledge and focuses only on non-obvious, Rust-specific conventions. The main weakness is the lack of executable code examples, which would make some guidelines more immediately actionable.
Suggestions
Add 1-2 executable code examples for the conversion naming conventions (as_/to_/into_) showing the actual function signatures and usage patterns
Include a brief code snippet demonstrating the newtype pattern with Email(String) to make that guideline immediately copy-paste ready
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. Uses tables for maximum information density, avoids explaining basic Rust concepts Claude already knows, and explicitly acknowledges 'Claude knows Rust conventions well' at the end. | 3 / 3 |
Actionability | Provides concrete naming patterns and specific alternatives (e.g., OnceLock over lazy_static), but lacks executable code examples. The guidance is specific but not copy-paste ready - it's more reference than instruction. | 2 / 3 |
Workflow Clarity | This is a reference/style guide skill, not a multi-step workflow skill. For its purpose (quick lookup of coding conventions), the table format provides clear, unambiguous guidance for each rule. | 3 / 3 |
Progressive Disclosure | Well-organized into logical sections (Naming, Data Types, Strings, etc.) with a Quick Reference summary. Under 50 lines, single-purpose reference skill that doesn't need external file references. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- actionbook/rust-skills
- Commit
1f4becd
- 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.