coding-standards
Universal coding standards, best practices, and patterns for TypeScript, JavaScript, React, and Node.js development.
Install with Tessl CLI
npx tessl i github:affaan-m/everything-claude-code --skill coding-standardsOverall
score
55%
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/skillValidation for skill structure
Discovery
33%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 its technology domain clearly but fails to provide explicit trigger guidance for when Claude should use this skill. It lacks concrete action verbs and natural user phrases, making it difficult for Claude to distinguish when to select this skill over other coding-related skills.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user asks about code style, naming conventions, project structure, or best practices for TypeScript, JavaScript, React, or Node.js projects'.
Include specific concrete actions such as 'Enforces naming conventions, recommends project structure, applies consistent formatting patterns, and guides component architecture'.
Add natural user phrases as trigger terms: 'code review', 'style guide', 'how should I organize', 'what's the best way to', 'coding conventions'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (TypeScript, JavaScript, React, Node.js) and mentions 'coding standards, best practices, and patterns' but doesn't list specific concrete actions like 'enforce naming conventions', 'apply linting rules', or 'structure components'. | 2 / 3 |
Completeness | Describes what (coding standards/best practices for specific technologies) but completely lacks a 'Use when...' clause or any explicit guidance on when Claude should select this skill. Missing the 'when' component caps this at 1. | 1 / 3 |
Trigger Term Quality | Includes relevant technology keywords (TypeScript, JavaScript, React, Node.js) that users might mention, but lacks natural trigger phrases users would say like 'code review', 'style guide', 'how should I structure', 'best way to write'. | 2 / 3 |
Distinctiveness Conflict Risk | The technology stack (TypeScript, JavaScript, React, Node.js) provides some specificity, but 'coding standards' and 'best practices' are generic enough to potentially conflict with other coding-related skills or language-specific skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides comprehensive, actionable code examples for TypeScript/React development with clear good/bad comparisons. However, it's overly verbose with explanations of principles Claude already knows, and the monolithic structure makes it token-inefficient. The content would benefit from being split into focused sub-documents with a lean overview.
Suggestions
Remove explanations of universal principles (KISS, DRY, YAGNI, 'code is read more than written') - Claude knows these; keep only the project-specific applications
Split into focused files: TYPESCRIPT.md, REACT.md, API.md, TESTING.md with a brief SKILL.md overview linking to each
Add a workflow section describing how to apply these standards during code review or development (e.g., 'Before committing: 1. Check for code smells, 2. Verify type safety, 3. Run linter')
Remove redundant '❌ 不良' examples where the good example alone is sufficient - Claude can infer what not to do
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains useful patterns but includes explanations Claude already knows (KISS, DRY, YAGNI principles, basic concepts like 'code is read more than written'). The code examples are good but surrounded by unnecessary commentary. | 2 / 3 |
Actionability | Excellent executable code examples throughout - TypeScript patterns, React components, API routes, and test structures are all copy-paste ready with clear good/bad comparisons. | 3 / 3 |
Workflow Clarity | This is primarily a reference document of patterns rather than a workflow skill. While patterns are clearly presented, there's no sequenced process with validation checkpoints for applying these standards to actual code review or development tasks. | 2 / 3 |
Progressive Disclosure | This is a monolithic 400+ line document with no references to external files. Content like API design, testing standards, and React patterns could be split into separate focused documents with clear navigation from a concise overview. | 1 / 3 |
Total | 8 / 12 Passed |
Validation
69%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 / 16 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 |
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
- 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.