cc-skill-coding-standards

Universal coding standards, best practices, and patterns for TypeScript, JavaScript, React, and Node.js development.

Quality

51%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/cc-skill-coding-standards/SKILL.md

Quality

Content

50%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a thorough, code-rich standards reference with strong GOOD/BAD examples, but it is padded with explanations of basic concepts Claude already knows and presents everything in one large inlined file with no progressive disclosure or workflow structure.

Suggestions

Remove or compress the 'Code Quality Principles' section (Readability First/KISS/DRY/YAGNI) since these are concepts Claude already knows.

Split the per-domain standards (TypeScript/JavaScript, React, API design, testing) into separate reference files linked from a concise SKILL.md overview.

Drop filler lines like the closing 'Remember: Code quality is not negotiable' to improve token efficiency.

Dimension	Reasoning	Score
Conciseness	Sections like 'Readability First', 'KISS', 'DRY', and 'YAGNI' restate basic programming platitudes ('Code is read more than written', 'Simplest solution that works') that Claude already knows, and the ~520-line volume is padded with these plus a closing 'Remember: Code quality is not negotiable' remark, matching 'Noticeably verbose; several unnecessary explanations or padded sections'.	2 / 5
Actionability	It provides numerous copy-paste-ready GOOD/BAD TypeScript and React code pairs covering naming, immutability, error handling, hooks, and validation, with only minor gaps such as '// Implementation' placeholders in getMarket and searchMarkets.	4 / 5
Workflow Clarity	This is a reference/standards document rather than a multi-step workflow, so there is no sequence or validation checkpoint; the content is well-organized by topic but lacks any procedural flow beyond the closing 'When to Use'/'Limitations' notes.	3 / 5
Progressive Disclosure	All content lives in a single monolithic SKILL.md with no references/, scripts/, or assets/ bundle and no file-level split; section headers provide structure, but reference material that could reasonably live in separate files (TypeScript standards, React standards, API standards) is all inlined.	3 / 5
	Total	12 / 20 Passed

Description

52%Weight 40%Scale 1-5

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 clearly scopes the skill to TypeScript/JavaScript/React/Node but stays at the level of abstract nouns ('standards, best practices, patterns') with no concrete actions and no explicit 'Use when' trigger guidance. It is somewhat distinct thanks to the named stacks yet broad enough to risk overlap with related skills.

Suggestions

Replace abstract nouns with concrete actions, e.g. 'Enforces naming, immutability, error-handling, and typing conventions when writing or reviewing TypeScript/React/Node code.'

Add an explicit trigger clause such as 'Use when writing, reviewing, or refactoring TypeScript, JavaScript, React, or Node.js code.'

Drop 'Universal' to reduce overlap risk with project-specific coding skills.

Dimension	Reasoning	Score
Specificity	The phrase 'Universal coding standards, best practices, and patterns' names the domain (TS/JS/React/Node) but lists no concrete actions — 'standards, best practices, and patterns' are abstract nouns, not verbs like 'extract' or 'validate', matching the score-2 anchor 'Names the domain but actions are minimal or generic'.	2 / 5
Completeness	It gives a clear 'what' (coding standards for the named stacks) but includes no 'Use when...' clause or equivalent trigger guidance, which per the judging guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	'TypeScript, JavaScript, React, and Node.js' are exactly the natural technology names a user would say when asking for coding standards, giving good keyword coverage, though common variations/synonyms are absent.	4 / 5
Distinctiveness Conflict Risk	The named stacks give it some specificity, but 'Universal coding standards, best practices, and patterns' is broad and would overlap with many project- or task-specific coding skills.	3 / 5
	Total	12 / 20 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (532 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: sickn33/antigravity-awesome-skills
Path: skills/cc-skill-coding-standards/SKILL.md
Commit: 1f67c44

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.