typescript-tooling

Development tools, linting, and build config for TypeScript. Use when configuring ESLint, Prettier, Jest, Vitest, tsconfig, or any TS build tooling.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

77%

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

The body is dense and actionable with a strong, validated verification workflow, but it loses conciseness points to repeated guidance across sections, and its progressive disclosure is undermined by REFERENCE.md referencing two missing leaf files (testing-setup.md, ci-cd.md).

Suggestions

Deduplicate guidance repeated across Implementation Guidelines and Anti-Patterns — e.g., consolidate the strict-migration steps and the @ts-expect-error rule so each appears once, cross-referencing the other section instead of restating.

Fix the reference graph in references/REFERENCE.md: either create the referenced testing-setup.md and ci-cd.md files or inline that content, since the current second-level links are broken.

Consider whether the Jest/Vitest/CI config blocks in REFERENCE.md belong as a separate, well-named file or inline summary to keep the reference structure a clean single level deep.

Dimension	Reasoning	Score
Conciseness	Quotes show lean bullets assuming Claude's competence, but the strict-migration guidance ('start with strictNullChecks, then noImplicitAny...') is repeated in Implementation Guidelines and Anti-Patterns, and '@ts-expect-error over @ts-ignore' appears in three sections, so not every token earns its place — matching 'mostly efficient but could be tightened' rather than a 3.	2 / 3
Actionability	Quotes 'Use `tsc` for CI builds', 'tsc --noEmit', 'eslint --fix', '@typescript-eslint/recommended', 'strictNullChecks', and `getDiagnostics` provide specific, copy-paste-ready commands and config keys, matching the fully executable score-3 anchor.	3 / 3
Workflow Clarity	The 'Verification Workflow (Mandatory)' section gives a clear numbered sequence (getDiagnostics → tsc --noEmit → eslint --fix) with an explicit fallback, matching the anchor 'Clear sequence with explicit validation steps; feedback loops for error recovery'.	3 / 3
Progressive Disclosure	The body cleanly signals a one-level reference ('See [reference](references/REFERENCE.md)'), but the actual bundle shows REFERENCE.md itself points to testing-setup.md and ci-cd.md that do not exist — a broken second level of nesting — so structure is present but poorly organized, fitting score 2 rather than 3.	2 / 3
	Total	10 / 12 Passed

Description

90%

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 is strong: it has an explicit 'Use when' trigger clause, names concrete tools a user would say, and occupies a clear TypeScript-tooling niche. Its only weakness is that the action vocabulary is largely limited to 'configuring/build' rather than enumerating distinct concrete actions.

Dimension	Reasoning	Score
Specificity	Quotes 'Development tools, linting, and build config for TypeScript' and 'configuring ESLint, Prettier, Jest, Vitest, tsconfig' name the domain and concrete tools, but the action vocabulary is essentially one verb ('configuring/build') rather than multiple distinct concrete actions, so it is not comprehensive enough for a 3.	2 / 3
Completeness	The 'Use when configuring ESLint, Prettier, Jest, Vitest, tsconfig, or any TS build tooling' clause explicitly answers both what the skill does and when to use it, matching the score-3 anchor with an explicit trigger clause.	3 / 3
Trigger Term Quality	Quotes 'ESLint, Prettier, Jest, Vitest, tsconfig, ... TS build tooling' provide good coverage of the natural terms a user would actually say, matching the anchor 'Good coverage of natural terms users would say'.	3 / 3
Distinctiveness Conflict Risk	TypeScript build/lint/test tooling with named tools (ESLint, Vitest, tsconfig) is a clear niche with distinct triggers unlikely to overlap with other skills, matching the score-3 anchor.	3 / 3
	Total	11 / 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
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning

	Total	14 / 16 Passed

Repository: HoangNguyen0403/agent-skills-standard
Commit: 611f52a

Reviewed: 4 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.