cc-skill-coding-standards

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

1.24x

Quality

46%

Does it follow best practices?

Impact

98%

1.24x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/cc-skill-coding-standards/SKILL.md

The canonical home for this skill is cc-skill-coding-standards in sickn33/agentic-awesome-skills

Quality

Content

40%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, example-rich coding-standards reference that is highly actionable but noticeably verbose, restating well-known principles. It lacks any multi-step workflow or validation guidance and inlines everything into one long file with no progressive disclosure to supporting files.

Suggestions

Trim or remove sections that restate concepts Claude already knows (e.g., the KISS/DRY/YAGNI bullet definitions) and keep only stack-specific, non-obvious conventions to improve conciseness.

Replace the circular 'When to Use' closer with concrete trigger conditions and, where relevant, a short sequenced workflow with validation checkpoints for batch/destructive operations.

Split the large reference into bundle files (e.g., references/typescript.md, references/react.md, references/api-design.md) and keep SKILL.md as a concise overview with one-level-deep links to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The ~500-line body restates concepts Claude already knows (KISS/DRY/YAGNI definitions, 'Code is read more than written', what good naming is) and pads with bullet platitudes, matching the 'noticeably verbose; several unnecessary explanations or padded sections' anchor.	2 / 5
Actionability	It provides numerous concrete, mostly executable ✅/❌ code examples across naming, immutability, error handling, React, and validation, but several functions carry '// Implementation' placeholders leaving minor gaps, fitting 'mostly executable guidance with minor gaps'.	4 / 5
Workflow Clarity	This is a reference doc with no multi-step workflow or validation checkpoints, and the closing 'When to Use' section is circular ('applicable to execute the workflow or actions described in the overview'), matching the 'rough sequence present but many gaps; validation absent' level.	2 / 5
Progressive Disclosure	No bundle files exist (references/scripts/assets absent) and all ~500 lines are inlined in SKILL.md with no pointers to deeper material; despite clear section headers, content that would benefit from file splitting is monolithically inlined, fitting the 'minimal structure; content that belongs in separate files is inlined' anchor.	2 / 5
	Total	10 / 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 identifies its technology stack and domain but stops at abstract categories rather than concrete actions, and it omits any explicit 'when to use' trigger guidance. It is distinguishable yet broad enough to risk overlap with similar standards skills.

Suggestions

Add a 'Use when...' clause with concrete triggers, e.g. 'Use when writing or reviewing TypeScript, JavaScript, React, or Node.js code and the user asks for coding standards, conventions, or best practices.'

Replace abstract nouns ('standards, best practices, and patterns') with concrete verbs/actions such as 'enforce naming, immutability, and error-handling conventions' to raise specificity.

Narrow the scope or add a distinguishing niche (e.g., 'for a Next.js + Supabase + Zod stack') to reduce overlap with generic coding-standards skills.

Dimension	Reasoning	Score
Specificity	The description names the domain and tech stack ('TypeScript, JavaScript, React, and Node.js development') but offers no concrete actions — 'coding standards, best practices, and patterns' are categories, not actions like 'enforce', 'lint', or 'refactor', matching the 'names the domain but actions are minimal' anchor.	2 / 5
Completeness	It clearly answers 'what' (standards/best practices/patterns for the named stack) but contains no 'Use when...' clause or equivalent explicit trigger guidance, so completeness is capped at 3 per the rubric guidelines.	3 / 5
Trigger Term Quality	Natural user-facing terms are present ('TypeScript', 'JavaScript', 'React', 'Node.js', 'coding standards', 'best practices'), giving good keyword coverage; a few synonyms or related phrasings (e.g., 'linting', 'refactoring', 'code review') are missing, so it sits just below comprehensive.	4 / 5
Distinctiveness Conflict Risk	Naming four specific technologies narrows it beyond a fully generic skill, but 'Universal coding standards... applicable across all projects' (per the body) keeps it broad with real overlap risk against other coding-conventions skills, fitting the 'somewhat specific but could still overlap' anchor.	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 (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	14 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills/skills/cc-skill-coding-standards/SKILL.md
Commit: 57c135b

Reviewed: 2 days 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.