ts-library
Use when authoring TypeScript libraries or npm packages - covers project setup, package.json exports, build tooling (tsdown/unbuild), API design patterns, type inference tricks, testing, and publishing to npm. Use when bundling, configuring dual CJS/ESM output, or setting up release workflows.
100
Does it follow best practices?
Validation for skill structure
Discovery
100%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 an excellent skill description that clearly defines its scope (TypeScript library/npm package authoring), lists specific concrete capabilities, and provides explicit trigger conditions. The description uses appropriate third-person voice and includes natural developer terminology that would help Claude accurately select this skill when relevant.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'project setup, package.json exports, build tooling (tsdown/unbuild), API design patterns, type inference tricks, testing, and publishing to npm' plus 'bundling, configuring dual CJS/ESM output, setting up release workflows'. | 3 / 3 |
Completeness | Explicitly answers both what (covers project setup, build tooling, API design, testing, publishing) AND when ('Use when authoring TypeScript libraries or npm packages', 'Use when bundling, configuring dual CJS/ESM output, or setting up release workflows'). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'TypeScript libraries', 'npm packages', 'package.json', 'tsdown', 'unbuild', 'bundling', 'CJS/ESM', 'release workflows', 'publishing to npm'. These are terms developers naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on TypeScript library/npm package authoring with distinct triggers like 'npm packages', 'tsdown/unbuild', 'dual CJS/ESM', 'package.json exports' that wouldn't conflict with general TypeScript coding skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an exemplary skill file that demonstrates best practices across all dimensions. It provides a concise overview with actionable quick-start examples, clear workflow with validation steps, and well-organized progressive disclosure to detailed reference files. The explicit token budget awareness and 'load only what's relevant' guidance show sophisticated understanding of context window management.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No unnecessary explanations of what TypeScript or npm are. Every section serves a purpose - quick reference table, loading guidance, minimal code examples. Token counts are even documented. | 3 / 3 |
Actionability | Provides concrete, copy-paste ready package.json and tsdown.config.ts examples. The workflow steps are specific with exact commands ('pnpm build && pnpm pack --dry-run') and expected outputs to verify. | 3 / 3 |
Workflow Clarity | Clear 6-step workflow for new libraries with explicit validation checkpoint (step 4: verify build outputs include .mjs, .cjs, .d.ts). Each step links to the relevant reference file for details. | 3 / 3 |
Progressive Disclosure | Excellent structure with overview content in main file and 10 well-organized reference files for detailed topics. Clear navigation via table and checklist. Explicit instruction not to load all files at once. All references are one level deep. | 3 / 3 |
Total | 12 / 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.
- 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.