typescript-tooling
Development tools, linting, and build config for TypeScript. Use when configuring ESLint, Prettier, Jest, Vitest, tsconfig, or any TS build tooling.
88
87%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid skill description with excellent trigger terms and completeness. It clearly identifies when to use the skill and names specific tools that serve as strong discriminators. The main weakness is that the capability description could be more specific about what actions it performs (e.g., 'configure rules', 'resolve config conflicts', 'set up project scaffolding') rather than just naming the domain.
Suggestions
Add specific concrete actions like 'Sets up and configures ESLint rules, Prettier formatting, test runners, and TypeScript compiler options' to improve specificity beyond just naming the domain.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain ('Development tools, linting, and build config for TypeScript') and lists specific tools (ESLint, Prettier, Jest, Vitest, tsconfig), but doesn't describe concrete actions like 'configure', 'set up rules', 'resolve conflicts between tools'. The actions are implied by 'configuring' in the trigger clause but the capability description itself is vague. | 2 / 3 |
Completeness | Clearly answers both 'what' (development tools, linting, and build config for TypeScript) and 'when' (explicit 'Use when configuring ESLint, Prettier, Jest, Vitest, tsconfig, or any TS build tooling'). | 3 / 3 |
Trigger Term Quality | Includes highly natural keywords users would say: ESLint, Prettier, Jest, Vitest, tsconfig, 'TS build tooling', 'linting', 'build config', 'TypeScript'. These are terms developers naturally use when seeking help with these tools. | 3 / 3 |
Distinctiveness Conflict Risk | The description carves out a clear niche around TypeScript build tooling and specific tools (ESLint, Prettier, Jest, Vitest, tsconfig). This is distinct enough to avoid conflicts with general coding skills or other language-specific skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, concise skill that efficiently communicates TypeScript tooling best practices. Its main strength is the clear verification workflow with fallback paths and the lean anti-patterns section. The primary weakness is the lack of executable configuration examples (sample tsconfig.json, eslintrc) — the skill tells Claude what to configure but delegates all concrete examples to the reference file.
Suggestions
Add a minimal executable tsconfig.json or .eslintrc snippet inline to make the Implementation Guidelines section more copy-paste actionable, rather than relying entirely on the reference file for config examples.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It avoids explaining what ESLint, Prettier, or TypeScript are, assumes Claude's competence, and every bullet point delivers actionable, non-obvious guidance. The anti-patterns section is terse but informative. | 3 / 3 |
Actionability | Provides specific tool names, commands (`tsc --noEmit`, `eslint --fix`), and MCP tool references (`getDiagnostics`, `getHover`), but lacks executable config file examples (e.g., a sample tsconfig.json, .eslintrc, or .prettierrc). The guidance is concrete but not fully copy-paste ready. | 2 / 3 |
Workflow Clarity | The verification workflow is clearly sequenced (getDiagnostics → tsc --noEmit → eslint --fix) with an explicit fallback path. The incremental migration strategy (strictNullChecks → noImplicitAny → strictFunctionTypes) provides a clear sequence with an explicit anti-pattern warning against skipping steps. | 3 / 3 |
Progressive Disclosure | The skill provides a concise overview with well-signaled one-level-deep references to REFERENCE.md for config examples and linting patterns. Content is appropriately split between the overview and the reference file. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 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 | 9 / 11 Passed | |
- Repository
- HoangNguyen0403/agent-skills-standard
- Commit
4c72e76
- Reviewed
Table of Contents
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.