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
Pending
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 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. It reads more like a category label than a skill description.
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 'coding standards, best practices, and patterns' with specific concrete actions, e.g., 'Enforces naming conventions, recommends file/folder structure, applies error handling patterns, and guides component composition.'
Narrow the scope to reduce conflict risk — specify what makes this skill distinct from other TypeScript/React skills, such as whether it focuses on style guidelines, architectural patterns, or code review feedback.
| 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 verbose coding standards reference that explains many concepts Claude already knows (KISS, DRY, YAGNI, naming conventions, early returns, magic numbers). While the code examples are high quality and executable, the sheer volume of basic programming knowledge wastes significant token budget. The monolithic structure with no progressive disclosure or external references makes it poorly suited as a SKILL.md file.
Suggestions
Remove or drastically reduce sections on universal programming principles (KISS, DRY, YAGNI, readable naming, magic numbers, early returns) that Claude already knows — focus only on project-specific conventions or non-obvious patterns.
Split content into separate files (e.g., REACT_PATTERNS.md, API_STANDARDS.md, TESTING.md) and make SKILL.md a concise overview with links to each, improving progressive disclosure.
Reduce the file to project-specific decisions only: e.g., 'use Zod for validation', 'use this specific ApiResponse<T> interface', 'use supabase client pattern X' — things Claude wouldn't know without being told.
Add a quick-reference summary at the top (under 20 lines) listing the key non-obvious conventions, so Claude can get the essential information without reading 350+ lines.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | This skill extensively explains fundamental programming principles (KISS, DRY, YAGNI, readable naming, early returns, magic numbers) that Claude already knows well. The vast majority of content is basic coding knowledge that adds no new information for Claude, consuming significant token budget on universally known concepts. | 1 / 3 |
Actionability | The skill provides fully executable TypeScript/React code examples throughout, with clear PASS/FAIL patterns showing both correct and incorrect approaches. Code snippets are copy-paste ready and cover concrete scenarios like error handling, API responses, Zod validation, and React hooks. | 3 / 3 |
Workflow Clarity | The skill is organized into clear sections with logical grouping, but it's essentially a reference document of patterns rather than a workflow. There are no multi-step processes with validation checkpoints; it's a collection of independent best practices without sequencing or feedback loops. | 2 / 3 |
Progressive Disclosure | The content is a monolithic wall of text at ~350+ lines with no references to external files or any layered structure. All content from basic principles to testing to performance is inlined in a single document with no navigation aids or links to deeper resources. | 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
5df943e
- 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.