cc-skill-coding-standards

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

1.24x

Quality

45%

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-claude/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

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 well-structured, example-rich coding-standards reference, but it is over-long and teaches programming fundamentals Claude already knows rather than adding unique guidance. It also lacks any progressive disclosure into reference files.

Suggestions

Cut explanations of basic concepts Claude already knows (KISS/DRY/YAGNI definitions, "code is read more than written", good-vs-bad naming primers) and keep only project-specific conventions.

Move the bulk of the standards into separate reference files (e.g., references/react.md, references/api.md) and leave SKILL.md as a concise overview with one-level-deep links.

Add a concrete 'When to use this skill' trigger section that names specific situations instead of the generic placeholder sentence.

Dimension	Reasoning	Score
Conciseness	The ~520-line body extensively explains concepts Claude already knows (KISS, DRY, YAGNI, "code is read more than written", good vs bad variable names), making it noticeably verbose with several padded sections.	2 / 5
Actionability	It provides many concrete, copy-paste-ready TypeScript examples (naming, immutability, error handling, React hooks, Zod validation) with clear good/bad contrasts, giving mostly executable guidance with only minor gaps.	4 / 5
Workflow Clarity	Content is organized into topical sections but there is no sequenced multi-step workflow or validation checkpoints, and the closing 'When to Use' is generic, fitting the anchor for steps present but checkpoints missing.	3 / 5
Progressive Disclosure	There are no bundle files and the entire reference is inlined in one ~520-line document with good section headers, but content that belongs in separate reference files is not split out, matching the 'some structure but could be better organized' anchor.	3 / 5
	Total	12 / 20 Passed

Description

41%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 the tech stack and topic area but is overly broad and lacks concrete actions or an explicit trigger clause. It reads as a category label rather than a precise, triggerable capability statement.

Suggestions

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

Replace abstract nouns with concrete actions the skill performs (e.g., 'Reviews code for naming, immutability, and error-handling violations; suggests refactors') to lift specificity.

Narrow the scope from 'universal' to a distinct niche to reduce overlap conflict with other coding skills.

Dimension	Reasoning	Score
Specificity	The description names the domain ("TypeScript, JavaScript, React, and Node.js") but uses abstract nouns ("standards, best practices, and patterns") with no concrete actions, matching the anchor for naming the domain with minimal/generic actions.	2 / 5
Completeness	It gives a clear "what" but has no "Use when..." clause or equivalent trigger guidance, so per the judging guideline completeness is capped at 3.	3 / 5
Trigger Term Quality	It includes the tech-stack names users would naturally say (TypeScript, React, Node.js) but "best practices" and "patterns" are generic and it misses common variations/synonyms, fitting the anchor for some relevant keywords with gaps.	3 / 5
Distinctiveness Conflict Risk	"Universal coding standards" is very broad and would overlap with many coding-related skills, matching the anchor for very broad coverage with high overlap risk.	2 / 5
	Total	10 / 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-claude/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.