cc-skill-coding-standards
Universal coding standards, best practices, and patterns for TypeScript, JavaScript, React, and Node.js development.
43
14%
Does it follow best practices?
Impact
98%
1.24xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/cc-skill-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 effectively guide skill selection. It names a domain (TypeScript/JavaScript/React/Node.js development) but fails to specify concrete actions, lacks a 'Use when' clause, and covers such a wide scope that it would likely conflict with many other coding-related skills.
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 project directory structure, applies consistent error handling patterns, and guides component composition.'
Narrow the scope or add distinguishing details to reduce conflict risk, e.g., specify whether this covers linting rules, architectural patterns, or code review guidelines.
| 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 directories'). | 1 / 3 |
Completeness | The 'what' is vague ('coding standards, best practices, and patterns') and there is no 'when' clause at all. Missing a 'Use when...' clause caps this at 2, and 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 lacks natural trigger phrases users would say like 'code review', 'refactor', 'style guide', 'lint', or 'code quality'. | 2 / 3 |
Distinctiveness Conflict Risk | This description is extremely broad — 'coding standards and best practices' could overlap with virtually any coding-related skill. The four listed technologies cover a huge portion of web development, making conflicts with other skills very likely. | 1 / 3 |
Total | 5 / 12 Passed |
Implementation
14%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an extensive but generic coding standards reference that explains concepts Claude already knows thoroughly (DRY, KISS, YAGNI, naming conventions, REST patterns, React basics). It consumes a very large token budget without providing project-specific, novel, or actionable guidance. The content would benefit enormously from being trimmed to only project-specific conventions and patterns that deviate from standard practices.
Suggestions
Remove all universally known programming concepts (KISS, DRY, YAGNI, basic naming, REST conventions, AAA testing) and keep only project-specific standards or non-obvious conventions that Claude wouldn't already follow.
Split the monolithic document into focused sub-files (e.g., REACT_PATTERNS.md, API_STANDARDS.md, TESTING.md) with a concise overview in the main skill file linking to each.
Add a concrete workflow for how to apply these standards—e.g., a code review checklist or steps to run linting/validation tools specific to the project.
Reduce the content to under 100 lines by focusing only on decisions that are non-obvious or project-specific (e.g., the specific API response format, the specific project structure, the immutability requirement).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | This skill is extremely verbose, explaining fundamental concepts Claude already knows well (KISS, DRY, YAGNI, basic naming conventions, what REST APIs are, AAA testing pattern). Nearly every section covers universally known programming principles with extensive good/bad examples that add little novel value. At ~350+ lines, the token cost is very high relative to the information density. | 1 / 3 |
Actionability | The code examples are concrete and executable, which is good. However, the guidance is generic best-practices rather than project-specific actionable instructions. There are no specific commands to run, no tool usage patterns, and no workflow steps—it reads more like a textbook reference than an operational skill. | 2 / 3 |
Workflow Clarity | There is no workflow or sequenced process described. The skill is a collection of coding standards and patterns with no multi-step process, validation checkpoints, or feedback loops. Even for a standards document, there's no guidance on how to apply or enforce these standards. | 1 / 3 |
Progressive Disclosure | The content is a monolithic wall of text with no references to external files or any layered structure. All content—from basic naming conventions to performance optimization to testing—is inlined in a single massive document with no navigation aids or separation of concerns. | 1 / 3 |
Total | 5 / 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 | |
- Repository
- sickn33/antigravity-awesome-skills
- Commit
6a07b83
- 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.