CtrlK
BlogDocsLog inGet started
Tessl Logo

code-standards

Enforces project-specific coding conventions by loading language standards before writing code. Use when about to write, edit, modify, or generate Go, Rust, Python, Tailwind CSS, or HCL (Terraform/OpenTofu) files. Loads once per language per session and overrides default style with project conventions. DO NOT TRIGGER for languages other than Go, Rust, Python, Tailwind CSS, or HCL (Terraform/OpenTofu).

71

Quality

86%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

72%

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 routing skill that efficiently maps file patterns to language-specific standards files. Its main weakness is the lack of concrete tool invocation examples and missing error handling for cases where standards files don't exist. The workflow is understandable but would benefit from explicit sequencing and edge case handling.

Suggestions

Add an explicit example of the Read tool invocation, e.g., `Read file: ../../code-standards/go/CLAUDE.md` to make the loading step fully actionable.

Add a brief error handling note for when a standards file is missing or unreadable (e.g., 'If the standards file does not exist, proceed with default conventions and note the missing file to the user').

DimensionReasoningScore

Conciseness

The skill is lean and efficient. It avoids explaining what coding standards are or how languages work. Every section serves a clear purpose: detection table, loading instruction, application rule. No wasted tokens.

3 / 3

Actionability

The language detection table with file patterns and paths is concrete and useful. However, the 'Loading Standards' and 'Applying Standards' sections are somewhat vague — they mention using 'the Read tool' but don't show the exact invocation, and 'follow these standards' is abstract guidance without showing how to handle conflicts between defaults and project conventions.

2 / 3

Workflow Clarity

The workflow is implicit rather than explicitly sequenced: detect language → check if already loaded → read file → apply standards. There's no validation step (e.g., what to do if the standards file doesn't exist or can't be read), and the session-caching logic ('only load once per language per session') lacks guidance on how to track what's been loaded.

2 / 3

Progressive Disclosure

The skill is appropriately structured as a concise overview that delegates detailed standards to separate per-language CLAUDE.md files via clear one-level-deep references. The table format makes navigation easy. For a skill under 50 lines with clear external references, this is well-organized.

3 / 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 an excellent skill description that clearly communicates what the skill does (enforces coding conventions by loading language standards), when to use it (when writing/editing code in specific languages), and when NOT to use it (other languages). It uses third person voice, includes natural trigger terms, and has strong boundary conditions that minimize conflict with other skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions: 'loading language standards before writing code', 'enforces project-specific coding conventions', and specifies exact languages (Go, Rust, Python, Tailwind CSS, HCL). Also describes behavior like 'loads once per language per session' and 'overrides default style with project conventions'.

3 / 3

Completeness

Clearly answers both 'what' (enforces project-specific coding conventions by loading language standards) and 'when' (when about to write, edit, modify, or generate files in the specified languages). Has an explicit 'Use when...' clause with clear triggers and even includes a negative boundary condition.

3 / 3

Trigger Term Quality

Includes highly natural trigger terms users would use: 'write', 'edit', 'modify', 'generate', and specific language names (Go, Rust, Python, Tailwind CSS, HCL, Terraform, OpenTofu). These are terms users would naturally say when requesting code work. The negative trigger ('DO NOT TRIGGER for languages other than...') also helps with precision.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive with a clear niche: project-specific coding conventions for exactly five named languages. The explicit exclusion clause ('DO NOT TRIGGER for languages other than...') further reduces conflict risk with other coding-related skills.

3 / 3

Total

12

/

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
shousper/claude-kit
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.