code-standards
Load language-specific coding standards before editing Go, Rust, Python, or Tailwind CSS files
79
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillEvaluation — 100%
↑ 1.00xAgent success when using this skill
Validation for skill structure
Discovery
50%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 identifies a clear purpose (loading coding standards) and specific technologies, but lacks explicit trigger guidance and comprehensive action details. It would benefit from a 'Use when...' clause and more natural trigger terms users might say when needing coding standards applied.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when editing Go, Rust, Python, or Tailwind CSS files, or when the user mentions code style, formatting standards, or linting.'
Include common variations of language names: 'golang', '.go files', '.py', '.rs', 'rustlang', 'CSS utilities'
Specify what 'load coding standards' means concretely: 'Applies language-specific formatting rules, naming conventions, and best practices'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (coding standards) and specific languages (Go, Rust, Python, Tailwind CSS), but the action 'Load...before editing' is somewhat vague - doesn't specify what loading entails or what standards are applied. | 2 / 3 |
Completeness | Describes what it does (load coding standards before editing specific file types) but lacks an explicit 'Use when...' clause. The 'when' is only implied through the file types mentioned. | 2 / 3 |
Trigger Term Quality | Includes specific language names (Go, Rust, Python, Tailwind CSS) which users would mention, but lacks common variations like 'golang', '.py files', 'style guide', 'linting', or 'code style'. | 2 / 3 |
Distinctiveness Conflict Risk | The specific language list helps distinguish it, but 'coding standards' and 'editing files' could overlap with general code editing or linting skills. The scope is clearer than generic but not fully distinct. | 2 / 3 |
Total | 8 / 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, concise skill that efficiently communicates when and how to load language-specific coding standards. The main weakness is the lack of a concrete example showing the Read tool invocation, which would make the skill more immediately actionable.
Suggestions
Add a brief example showing the exact Read tool invocation, e.g., `Read("../../code-standards/go/CLAUDE.md")` to make the loading step copy-paste ready
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, providing only essential information: a detection table, loading instructions, and application guidance. No unnecessary explanations of what coding standards are or how languages work. | 3 / 3 |
Actionability | Provides clear file patterns and paths, but lacks concrete examples of how to use the Read tool or what the loaded standards might look like. The instruction 'Use the Read tool' is somewhat vague without showing the exact invocation. | 2 / 3 |
Workflow Clarity | For this simple skill, the workflow is clear: detect language → load standards (once) → apply standards. The single-load-per-session constraint is explicit, and the sequence is unambiguous. | 3 / 3 |
Progressive Disclosure | Appropriately structured with clear sections. References to external standards files are one level deep and clearly signaled in the table. The skill itself is concise and delegates detailed standards to separate files. | 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.
- 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.