coding-standards
Universal coding standards, best practices, and patterns for TypeScript, JavaScript, React, and Node.js development.
32
28%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.claude/skills/coding-standards/SKILL.mdQuality
Discovery
14%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 description is too vague and broad to be effective for skill selection. It names a technology domain but fails to specify concrete actions, lacks a 'Use when...' clause, and uses generic terms like 'best practices' and 'patterns' that would cause conflicts with many other coding-related skills.
Suggestions
Add a 'Use when...' clause specifying explicit triggers, e.g., 'Use when the user asks about coding conventions, naming standards, project structure, or style guidelines for TypeScript/React/Node.js projects.'
Replace vague terms like 'best practices and patterns' with concrete actions, e.g., 'Enforces naming conventions, defines file/folder structure, applies error handling patterns, and configures linting rules.'
Narrow the scope to reduce conflict risk — clarify what distinguishes this from other TypeScript/React skills (e.g., is this about style/conventions specifically, as opposed to implementation or debugging?).
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'coding standards, best practices, and patterns' without listing any concrete actions. It doesn't specify what the skill actually does (e.g., 'enforces naming conventions', 'applies linting rules', 'structures project directories'). | 1 / 3 |
Completeness | The description partially addresses 'what' (coding standards and best practices) but in very vague terms, and completely lacks a 'when' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | It includes relevant technology keywords (TypeScript, JavaScript, React, Node.js) that users might mention, but lacks natural trigger phrases users would say like 'code review', 'refactor', 'style guide', 'lint', or 'code quality'. The terms 'coding standards' and 'best practices' are somewhat generic. | 2 / 3 |
Distinctiveness Conflict Risk | This description is extremely broad and would conflict with virtually any TypeScript, JavaScript, React, or Node.js coding skill. 'Universal coding standards' and 'best practices' could overlap with linting skills, code review skills, project scaffolding skills, and many others. | 1 / 3 |
Total | 5 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is a comprehensive but extremely verbose coding standards reference that explains many concepts Claude already knows well (KISS, DRY, YAGNI, basic naming conventions, conditional rendering patterns). While the code examples are high quality and executable, the document would be far more effective as a concise overview pointing to separate reference files for each domain (React, API design, testing, etc.), focusing only on project-specific conventions that deviate from standard practices.
Suggestions
Remove explanations of universal principles Claude already knows (KISS, DRY, YAGNI, readability) and focus only on project-specific conventions or deviations from standard practices.
Split into multiple files: keep SKILL.md as a brief overview (<50 lines) with references to separate files like REACT.md, API_DESIGN.md, TESTING.md for detailed patterns.
Remove basic examples (variable naming, conditional rendering, lazy loading) that any competent developer or LLM would know, and keep only non-obvious or project-specific patterns like the immutability requirement or specific response format.
Add a workflow for how to actually apply these standards during code review or refactoring, with validation steps (e.g., run linter, check types, verify test coverage).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~350+ lines. Extensively explains principles Claude already knows (KISS, DRY, YAGNI, readability). Many examples cover basic patterns (variable naming, conditional rendering, lazy loading) that Claude is deeply familiar with. Very little here is novel or project-specific information that Claude couldn't generate on its own. | 1 / 3 |
Actionability | The skill provides fully executable TypeScript/React code examples throughout, with clear good/bad comparisons. Code snippets are copy-paste ready and cover concrete patterns like error handling, Zod validation, custom hooks, and test structure. | 3 / 3 |
Workflow Clarity | The skill is organized into clear sections with logical grouping, but it's a reference document rather than a workflow. There are no multi-step processes with validation checkpoints. The 'When to Activate' section lists triggers but doesn't sequence how to apply these standards in practice. | 2 / 3 |
Progressive Disclosure | Monolithic wall of content with no references to external files. All content is inline despite being far too long for a single SKILL.md. Sections like React Best Practices, API Design, Testing Standards, and Performance could each be separate referenced files. | 1 / 3 |
Total | 7 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (531 lines); consider splitting into references/ and linking | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Repository
- devrev/meerkat
- Commit
b09913f
- 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.