coding-standards
Universal coding standards, best practices, and patterns for TypeScript, JavaScript, React, and Node.js development.
42
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 ./docs/zh-TW/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 generic to effectively differentiate itself from other coding-related skills. It lacks concrete actions, explicit trigger guidance, and sufficient specificity to prevent conflicts with other skills covering the same technology stack. The broad terms 'best practices' and 'patterns' provide almost no discriminative value.
Suggestions
Add a 'Use when...' clause specifying explicit triggers, e.g., 'Use when the user asks about code style, naming conventions, project structure, or best practices for TypeScript/React/Node.js projects.'
Replace vague terms like 'best practices and patterns' with concrete actions, e.g., 'Enforces naming conventions, recommends file/folder structure, applies error handling patterns, and guides component composition in React.'
Narrow the scope or add distinguishing details to reduce conflict risk with other coding skills, e.g., specifying whether this covers linting rules, architectural patterns, or code review guidance.
| 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 it actually does (e.g., 'enforces naming conventions', 'applies linting rules', 'structures project files'). | 1 / 3 |
Completeness | The 'what' is vague (standards, best practices, patterns) and there is no 'when' clause at all. There's no explicit guidance on when Claude should select this skill, which per the rubric caps completeness at 2 at best, but the weak 'what' brings it to 1. | 1 / 3 |
Trigger Term Quality | It includes relevant technology keywords (TypeScript, JavaScript, React, Node.js) that users might mention, but 'coding standards' and 'best practices' are broad terms. It misses natural trigger phrases users would say like 'code review', 'style guide', 'conventions', 'how should I structure'. | 2 / 3 |
Distinctiveness Conflict Risk | This description is extremely broad and would conflict with virtually any TypeScript, JavaScript, React, or Node.js coding skill. 'Best practices' and 'patterns' could apply to almost any development-related skill. | 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 verbose coding standards document that teaches Claude things it already knows (KISS, DRY, YAGNI, naming conventions, early returns, etc.). While the code examples are high-quality and executable, the sheer volume of well-known best practices wastes context window tokens. The monolithic structure with no progressive disclosure makes it particularly expensive to load for any single task.
Suggestions
Remove or drastically reduce coverage of universal programming principles (KISS, DRY, YAGNI, naming conventions, early returns, magic numbers) that Claude already knows — focus only on project-specific conventions or non-obvious patterns.
Split the monolithic file into focused reference files (e.g., react-patterns.md, api-standards.md, testing.md) and make SKILL.md a concise overview with links to each.
Add a brief section on how to apply/verify these standards (e.g., 'Run eslint before committing', 'Check these 3 things in code review') to improve workflow clarity.
Reduce the file to under 100 lines by keeping only project-specific decisions (e.g., 'use Zod for validation', 'use this specific API response format', 'use this project structure') rather than general best practices.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | This skill extensively explains fundamental programming concepts Claude already knows well — KISS, DRY, YAGNI, naming conventions, early returns, magic numbers, immutability, etc. These are textbook software engineering principles that add no new knowledge. The file is ~350 lines of content that could be reduced to a fraction by focusing only on project-specific conventions. | 1 / 3 |
Actionability | The skill provides fully executable TypeScript/React code examples throughout, with clear PASS/FAIL patterns, concrete interface definitions, and copy-paste ready snippets for every concept covered. | 3 / 3 |
Workflow Clarity | This is primarily a standards/conventions document rather than a multi-step workflow, so explicit sequencing is less critical. However, there are no validation checkpoints or feedback loops for applying these standards (e.g., linting steps, review checklists), and the content is presented as a flat list of rules without clear prioritization or decision flow. | 2 / 3 |
Progressive Disclosure | The content is a monolithic wall of text covering TypeScript, React, API design, file organization, testing, performance, and code smells all in one file with no references to supporting documents. This would benefit greatly from splitting into focused files (e.g., react-patterns.md, api-standards.md, testing.md) with a concise overview in the main SKILL.md. | 1 / 3 |
Total | 7 / 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 |
|---|---|---|
skill_md_line_count | SKILL.md is long (521 lines); consider splitting into references/ and linking | Warning |
Total | 10 / 11 Passed | |
- Repository
- affaan-m/everything-claude-code
- Commit
841beea
- 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.