coding-standards

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

Quality

63%

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 ./docs/zh-TW/skills/coding-standards/SKILL.md

Quality

Content

73%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 highly actionable and well-organized with concrete PASS/FAIL code examples, but it is a monolithic single-file reference with no progressive disclosure and some explanation of concepts Claude already knows.

Suggestions

Split large reference sections (API design, file organization, testing standards) into separate reference files and link to them from SKILL.md to enable progressive disclosure.

Remove definitions of well-known principles (KISS, DRY, YAGNI) and the closing '記住' line to tighten token efficiency.

Add a brief overview/quick-start section at the top that points to the separated reference files.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and code-forward with brief comments, but it explains concepts Claude already knows (KISS, DRY, YAGNI definitions) and includes a redundant closing '記住' line that could be trimmed.	3 / 5
Actionability	Provides copy-paste-ready, executable TypeScript examples in PASS/FAIL pairs covering naming, immutability, error handling, React hooks, API design, and testing across common cases.	5 / 5
Workflow Clarity	This is a single-purpose reference skill with no multi-step process; the simple-skill exception applies and the content is unambiguously organized by clear section headers.	5 / 5
Progressive Disclosure	All ~500 lines of content live in one monolithic SKILL.md with no bundle files and no external references, despite distinct topics (API reference, file organization, testing) that clearly belong in separate files.	2 / 5
	Total	15 / 20 Passed

Description

53%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 names a clear domain and stack but relies on generic deliverables, lacks a 'Use when' trigger clause, and is broad enough to risk overlap with many related skills.

Suggestions

Add a 'Use when ...' clause listing concrete trigger phrases (e.g., 'Use when writing or reviewing TypeScript, React, or Node.js code, or when the user asks for coding standards or best practices').

Replace generic terms ('standards, best practices, patterns') with concrete actions such as 'enforce naming, immutability, error-handling, and testing conventions'.

Narrow scope or add a distinguishing qualifier to reduce overlap with general language-specific skills.

Dimension	Reasoning	Score
Specificity	Names the domain concretely (TypeScript, JavaScript, React, Node.js) but describes only generic deliverables ('standards, best practices, patterns') rather than concrete actions like enforcing, linting, or reviewing.	3 / 5
Completeness	States clearly what the skill provides but contains no 'Use when...' trigger clause, which caps completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Includes natural terms users say ('coding standards', 'best practices', 'React', 'Node.js') with good coverage, though it omits synonyms and file extensions beyond the named languages.	4 / 5
Distinctiveness Conflict Risk	'Universal coding standards' is very broad and would overlap with virtually any TypeScript/JavaScript/React/Node skill, with no distinct niche to reduce conflict risk.	2 / 5
	Total	12 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (521 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: affaan-m/ECC
Path: docs/zh-TW/skills/coding-standards/SKILL.md
Commit: e04ea0b

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.