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.
99
100%
Does it follow best practices?
Impact
98%
1.92xAverage score across 3 eval scenarios
Passed
No known issues
Quality
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 a strong skill description that clearly defines its scope around TypeScript library and npm package authoring. It provides rich, specific trigger terms covering the full lifecycle from setup to publishing, and includes explicit 'Use when' guidance that makes it easy for Claude to select appropriately. The mention of specific tools (tsdown/unbuild) and technical concepts (dual CJS/ESM) further sharpens its distinctiveness.
| 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, publishing to npm, bundling, configuring dual CJS/ESM output, and setting up release workflows. | 3 / 3 |
Completeness | Clearly answers both what (covers project setup, build tooling, API design, type inference, testing, publishing) and when (authoring TypeScript libraries/npm packages, bundling, configuring dual output, setting up release workflows) with explicit 'Use when' clauses. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'TypeScript libraries', 'npm packages', 'package.json', 'exports', 'tsdown', 'unbuild', 'bundling', 'CJS/ESM', 'publishing to npm', 'release workflows'. These are terms developers naturally use when working in this domain. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche focused specifically on TypeScript library/npm package authoring with specific tooling mentions (tsdown/unbuild) and domain-specific concepts (dual CJS/ESM output, package.json exports). Unlikely to conflict with general TypeScript coding skills or application development 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 serves as a well-structured hub for TypeScript library development. It provides just enough inline content (minimal package.json, tsdown config, key principles) to be immediately useful while delegating detailed guidance to clearly organized reference files. The dual navigation aids (table + checklist) and explicit workflow with validation make this highly effective.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient. It assumes Claude's competence with TypeScript and library development, avoids explaining basic concepts, and uses tables and checklists for quick scanning. The token budget note at the bottom is a nice touch. The only minor redundancy is the 'Loading Files' checklist duplicating the 'Quick Reference' table, but both serve slightly different purposes (lookup vs. task-based loading). | 3 / 3 |
Actionability | Provides concrete, copy-paste-ready package.json and tsdown.config.ts examples. The workflow steps include a specific verification command ('pnpm build && pnpm pack --dry-run') with expected outputs. Key principles are specific and prescriptive rather than vague. | 3 / 3 |
Workflow Clarity | The 'New Library Workflow' section provides a clear 6-step sequence with an explicit validation checkpoint at step 4 (verify build with specific command and expected output files). Each step links to the relevant reference file. The workflow is well-sequenced and includes verification before proceeding to testing and release. | 3 / 3 |
Progressive Disclosure | Excellent progressive disclosure pattern. The main skill is a concise overview with a quick reference table, task-based loading checklist, and clear one-level-deep references to 10 separate files. The explicit instruction 'DO NOT load all files at once' reinforces selective loading. Navigation is clear and well-signaled. | 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.
- Repository
- onmax/nuxt-skills
- Commit
00fb59d
- 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.