cc-skill-coding-standards

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

Quality

42%

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

35%

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

This is a large, generic coding-standards reference catalog of GOOD/BAD pattern examples covering territory Claude already knows, with no workflow sequencing or progressive disclosure. It is actionable as a pattern reference but verbose and poorly structured for token efficiency.

Suggestions

Trim or remove explanations of concepts Claude already knows (KISS, DRY, YAGNI, magic numbers, deep nesting) and keep only the project-specific conventions that differ from common knowledge.

Split the detailed language/React/API standards into separate reference files (e.g., REACT.md, API.md) and leave a concise overview with one-level-deep links in SKILL.md.

Add a brief workflow or checklist for applying the standards (e.g., review naming -> types -> error handling -> validation) with a verification checkpoint.

Dimension	Reasoning	Score
Conciseness	The ~500-line body explains well-known concepts Claude already knows (DRY, KISS, YAGNI, immutability, naming, magic numbers) and is padded with extensive GOOD/BAD example pairs, fitting the verbose score-1 anchor.	1 / 3
Actionability	Concrete TypeScript/React code examples with GOOD/BAD pairs are present, but they illustrate generic patterns rather than giving copy-paste-ready, task-specific executable guidance.	2 / 3
Workflow Clarity	Content is organized into labeled sections, but there is no multi-step workflow, no sequence for applying the standards, and no validation checkpoints for risky operations.	2 / 3
Progressive Disclosure	The file has clear section headers, but everything is inline in one monolithic document with no bundle files or one-level-deep references to split out the detailed reference material.	2 / 3
	Total	7 / 12 Passed

Description

50%

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 names the technology stack and high-level scope but offers no concrete actions and no explicit trigger guidance, leaving Claude without a clear 'when to use this' signal. It reads as a domain label rather than a triggering description.

Suggestions

Add concrete actions (e.g., 'enforce naming conventions, immutability patterns, and error-handling standards') instead of the vague 'best practices, and patterns'.

Append an explicit 'Use when...' clause naming natural trigger phrases (e.g., 'Use when reviewing TypeScript/React code, setting up project conventions, or refactoring Node.js modules').

Tighten distinctiveness by scoping to a specific niche rather than 'Universal' to reduce overlap with other coding-quality skills.

Dimension	Reasoning	Score
Specificity	Names the domain ('TypeScript, JavaScript, React, and Node.js') and broad action categories ('standards, best practices, and patterns') but lists no concrete actions like the score-3 anchor requires.	2 / 3
Completeness	It states what the skill covers but provides no 'Use when...' clause or equivalent explicit trigger guidance, so completeness is capped at 2 per the guidelines.	2 / 3
Trigger Term Quality	The technology names ('TypeScript, JavaScript, React, Node.js') are natural terms users say, but there are no common task-level trigger variations and no 'Use when' phrasing.	2 / 3
Distinctiveness Conflict Risk	'Universal coding standards' is generic and would overlap with many code-quality skills, though the named tech stack gives it a partial niche rather than full generality.	2 / 3
	Total	8 / 12 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: a3068b7

Reviewed: about 13 hours 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.