typescript-tooling
Development tools, linting, and build config for TypeScript. Use when configuring ESLint, Prettier, Jest, Vitest, tsconfig, or any TS build tooling. (triggers: tsconfig.json, .eslintrc.*, jest.config.*, package.json, eslint, prettier, jest, vitest, build, compile, lint)
84
80%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.github/skills/typescript/typescript-tooling/SKILL.mdQuality
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 strong skill description with excellent trigger term coverage and clear 'when to use' guidance. Its main weakness is that the 'what' portion is somewhat generic—it says 'configuring' but doesn't enumerate specific actions like creating configs, debugging build errors, or migrating between tools. The explicit triggers list is a nice touch that compensates for some of the specificity gap.
Suggestions
Add more specific concrete actions beyond 'configuring', such as 'create and debug TypeScript configs, set up linting rules, configure test runners, resolve build errors'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (TypeScript development tools) and lists specific tools (ESLint, Prettier, Jest, Vitest, tsconfig), but doesn't describe concrete actions—it says 'configuring' generically rather than listing specific tasks like 'set up linting rules, configure test runners, define compiler options'. | 2 / 3 |
Completeness | Clearly answers both 'what' (development tools, linting, and build config for TypeScript) and 'when' (explicit 'Use when...' clause with specific tool names and scenarios, plus a triggers list). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including both tool names (ESLint, Prettier, Jest, Vitest) and file patterns (tsconfig.json, .eslintrc.*, jest.config.*, package.json) as well as action words (build, compile, lint) that users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to TypeScript build tooling and configuration with very specific file patterns and tool names, making it unlikely to conflict with general coding skills or other language-specific skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
70%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid skill file with good structure, a clear verification workflow, and appropriate progressive disclosure. Its main weaknesses are moderate verbosity (excessive bold formatting, some unnecessary framing) and incomplete actionability—several recommendations lack executable examples (e.g., ESLint config, Prettier setup, tsup/Vite config). The common linting issues section is a strong practical addition.
Suggestions
Add a concrete, copy-paste-ready ESLint config example (e.g., .eslintrc.cjs with @typescript-eslint/recommended and strict type-checked rules) to match the level of specificity given to tsconfig.json.
Remove the 'Priority: P1 (OPERATIONAL)' header and the 'Essential tooling for TypeScript development and maintenance' line—these add no actionable value for Claude.
Reduce excessive bold formatting throughout the Implementation Guidelines section; the heavy bolding adds visual noise without improving clarity.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient but includes some unnecessary bolding/formatting noise and a few explanatory phrases Claude wouldn't need (e.g., 'Essential tooling for TypeScript development and maintenance', explaining what tsup and Vite are for). The priority label adds no value for Claude. | 2 / 3 |
Actionability | Provides some concrete guidance like specific tsconfig settings, code snippets for mock typing and request interfaces, and specific commands (tsc --noEmit, eslint --fix). However, the ESLint configuration section lacks an actual config file example, and many guidelines are directive rather than executable (e.g., 'Use tsup for library bundling' without showing how). | 2 / 3 |
Workflow Clarity | The verification workflow is clearly sequenced with three explicit steps, includes a fast feedback loop (getDiagnostics), and distinguishes between local and CI validation. The workflow covers the critical validation checkpoint of running type checks before commits. | 3 / 3 |
Progressive Disclosure | Content is well-structured with clear sections, the main skill file covers essential information concisely, and advanced/CI/test setup details are appropriately deferred to a single reference file (references/REFERENCE.md) with a clear signal. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- HoangNguyen0403/agent-skills-standard
- Commit
19a1140
- 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.