cc-skill-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:sickn33/antigravity-awesome-skills --skill cc-skill-coding-standards62
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/skillEvaluation — 98%
↑ 1.24xAgent success when using this skill
Validation for skill structure
Discovery
32%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 but relies heavily on vague terms like 'best practices' and 'patterns' without concrete actions. The critical missing element is any 'Use when...' guidance, making it difficult for Claude to know when to select this skill over others. The technology keywords provide some distinctiveness but aren't sufficient for reliable skill selection.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when writing TypeScript/JavaScript code, reviewing React components, setting up Node.js projects, or when the user asks about coding conventions or style guidelines'.
Replace vague terms with specific actions: instead of 'best practices and patterns', list concrete capabilities like 'enforce naming conventions, structure React components, configure ESLint rules, organize project folders'.
Include natural user phrases as trigger terms: 'code style', 'how should I name', 'project structure', 'coding conventions', 'clean code'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (coding standards) and technologies (TypeScript, JavaScript, React, Node.js), but uses vague terms like 'best practices' and 'patterns' without listing concrete actions like 'enforce naming conventions' or 'apply linting rules'. | 2 / 3 |
Completeness | Describes what (coding standards and best practices) but completely lacks a 'Use when...' clause or any explicit guidance on when Claude should select this skill. The rubric caps completeness at 2 for missing 'Use when' and this also has weak 'what'. | 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', 'coding conventions', or 'how should I structure'. | 2 / 3 |
Distinctiveness Conflict Risk | The technology stack provides some specificity, but 'coding standards' and 'best practices' are generic enough to potentially conflict with language-specific skills, linting tools, or code review 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 highly actionable code examples with clear good/bad comparisons, making it useful as a reference. However, it's overly verbose for a skill file, explaining basic concepts Claude already knows and presenting everything in a single monolithic document. The content would benefit significantly from being restructured into a brief overview with links to detailed reference files.
Suggestions
Remove the 'Code Quality Principles' section (KISS, DRY, YAGNI) - Claude already knows these concepts
Split into multiple files: keep SKILL.md as a brief overview (~50 lines) with links to separate files for TypeScript standards, React patterns, API design, and testing
Add a quick-reference checklist at the top summarizing the most critical patterns (immutability, error handling, type safety) for fast scanning
Remove explanatory text like 'Code is read more than written' - focus only on the concrete patterns and examples
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | While the examples are clear and well-formatted, the skill includes explanations of concepts Claude already knows (KISS, DRY, YAGNI principles, basic React patterns). The 'Code Quality Principles' section is largely unnecessary padding. | 2 / 3 |
Actionability | Provides fully executable TypeScript/React code examples throughout, with clear good/bad comparisons. Code is copy-paste ready with proper imports and type definitions. | 3 / 3 |
Workflow Clarity | This is a reference/standards document rather than a workflow skill, so multi-step processes aren't the focus. However, the testing section mentions AAA pattern without showing a complete test workflow, and there's no guidance on how to apply these standards in sequence during development. | 2 / 3 |
Progressive Disclosure | Monolithic wall of text at ~400 lines with no references to external files. Content like API design standards, testing standards, and performance best practices could be split into separate reference files with clear navigation from a concise overview. | 1 / 3 |
Total | 8 / 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 (527 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 | |
- 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.