coding-standards

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

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

65%

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

The content is a well-organized, action-rich reference with strong executable TypeScript/React patterns, but it is an over-long monolith that re-teaches widely known best practices without splitting detail into reference files. It scores high on actionability and moderately on conciseness, workflow clarity, and progressive disclosure.

Suggestions

Trim or move concepts Claude already knows (immutability via spread, Promise.all, functional setState, DRY/YAGNI/KISS) and keep only project-specific conventions, to improve token efficiency.

Split the API design, code-smell catalog, and testing sections into one-level reference files linked from a concise SKILL.md overview to improve progressive disclosure.

Add a short decision flow or 'When to Activate' mapping that sequences which standard to apply in a given context, giving the reference a clearer workflow spine.

Dimension	Reasoning	Score
Conciseness	The ~530-line body restates general principles Claude already knows (spread-based immutability, Promise.all, functional setState, early returns vs deep nesting, DRY/YAGNI/KISS) with extensive GOOD/BAD pairs, so it is mostly efficient and concrete but includes substantial unnecessary explanation for a competent TS/React coder.	2 / 3
Actionability	Provides fully executable, copy-paste-ready patterns such as a typed useDebounce hook, a zod CreateMarketSchema, an ApiResponse<T> shape, a REST route table, and a JSDoc template, which matches concrete executable code with specific examples.	3 / 3
Workflow Clarity	It is a standards catalog with a 'When to Activate' list and clear sectioning, but no sequenced multi-step workflow or validation checkpoints, and the action of applying the right standard across many contexts remains diffuse; structure is present but explicit sequence/checkpoints are missing.	2 / 3
Progressive Disclosure	No bundle files exist and the entire body is a single monolithic SKILL.md with API conventions, code smells, testing, and performance all inline; internal headings give structure, but content that should be split into one-level reference files is kept inline.	2 / 3
	Total	9 / 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 identifies its domain and target ecosystems but stays at the topic level, omitting concrete actions and any explicit 'Use when' trigger guidance. It reads as a category label rather than a precise, well-triggered skill description.

Suggestions

Add an explicit 'Use when...' trigger clause naming concrete moments users would voice (e.g., 'Use when reviewing code quality, refactoring for consistency, or setting up linting/formatting rules for TypeScript, React, or Node.js').

Replace the abstract 'standards, best practices, and patterns' framing with specific actions the skill performs (e.g., 'enforces naming, immutability, error-handling, and testing conventions').

Narrow the scope or add distinctive triggers so it does not collide with dedicated React/TypeScript/testing skills.

Dimension	Reasoning	Score
Specificity	Names the domain and ecosystems ('TypeScript, JavaScript, React, and Node.js development') and broad categories ('standards, best practices, and patterns'), but lists no concrete actions like enforcing naming rules or formatting, so it stops at naming domain + some actions rather than multiple specific actions.	2 / 3
Completeness	It states what the skill covers but has no 'Use when...' or equivalent explicit trigger guidance, which per the guidelines caps completeness at 2 (has what, when is missing or only implied).	2 / 3
Trigger Term Quality	Offers technical category labels ('coding standards', 'best practices', 'patterns') and ecosystem names, but misses the natural phrasings users actually say ('review my code', 'refactor this', 'set up linting'), so it has some relevant keywords but lacks common variations.	2 / 3
Distinctiveness Conflict Risk	'Universal coding standards' spanning TS/JS/React/Node is broad and would overlap with dedicated React, TypeScript, testing, or linting skills, so it is somewhat specific but could still conflict with similar skills.	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 (531 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: devrev/meerkat
Commit: 8155fdc

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.