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, 命名规范, 代码风格, 格式化, 最佳实践, 代码审查, 怎么命名
Install with Tessl CLI
npx tessl i github:actionbook/rust-skills --skill coding-guidelines94
Does it follow best practices?
Validation for skill structure
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 clear 'Use when' guidance. The main weakness is that it relies heavily on keyword listing rather than describing concrete actions the skill performs. The Rust-specific terminology provides good distinctiveness.
Suggestions
Add 2-3 concrete action verbs describing what the skill does, e.g., 'Provides guidance on Rust naming conventions, formatting rules, and Clippy lint recommendations' rather than just listing keywords.
| 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 linting checks'. | 2 / 3 |
Completeness | Explicitly answers both 'what' (Rust code style/best practices guidance) and 'when' with a clear 'Use when asking about...' clause at the start, plus extensive keyword triggers for when to activate. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say including 'code style', 'best practice', 'naming convention', 'clippy', 'rustfmt', 'lint', 'code review', plus Chinese equivalents for international users. Includes both technical terms and natural language variations. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to Rust-specific style guidance with distinct triggers like 'clippy', 'rustfmt', 'P.NAM', 'G.FMT' that are unique to Rust ecosystem. Unlikely to conflict with general code style skills or other language-specific skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an exemplary skill file that maximizes information density through effective use of tables, provides concrete actionable guidance without explaining concepts Claude already knows, and organizes content logically for quick reference. The explicit acknowledgment that Claude knows Rust conventions and focus on 'non-obvious Rust-specific rules' demonstrates excellent understanding of skill file purpose.
| 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, specific guidance with exact naming patterns, code snippets, and direct comparisons (deprecated vs better). The quick reference section gives copy-paste ready patterns. | 3 / 3 |
Workflow Clarity | This is a reference/style guide skill, not a multi-step workflow. The single-purpose nature (code style lookup) is unambiguous, and the table format makes finding specific rules trivial. | 3 / 3 |
Progressive Disclosure | Well-organized into logical sections (Naming, Data Types, Strings, etc.) with a quick reference summary. For a compact reference skill under 100 lines, no external file references are needed. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 12 / 16 Passed | |
- 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.