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 niche in TypeScript library authoring and npm package publishing. It provides comprehensive trigger terms covering the full lifecycle from project setup to publishing, with explicit 'Use when' guidance. The specificity of tools and concepts mentioned (tsdown, unbuild, dual CJS/ESM, package.json exports) makes it highly distinguishable from related skills.
| 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' with explicit 'Use when' clauses at both the beginning and end of the description, specifying authoring TypeScript libraries, bundling, configuring dual 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', '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 targeting TypeScript library authoring and npm package publishing specifically. The mention of specific tools (tsdown/unbuild), dual CJS/ESM output, and package.json exports clearly distinguishes this from general TypeScript development or web application 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 excellent progressive disclosure, conciseness, and actionability. It serves as a hub document that provides just enough inline content (minimal package.json, tsdown config, key principles) to be immediately useful while delegating detailed guidance to well-organized reference files. The workflow section includes proper validation checkpoints and the dual navigation patterns (table + checklist) serve different use cases effectively.
| 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 every section serves a clear purpose. The token budget note at the bottom is a nice touch. The only minor redundancy is the Quick Reference table and Loading Files checklist covering the same references, but both serve distinct purposes (lookup vs. task-based loading). | 3 / 3 |
Actionability | Provides concrete, copy-paste ready package.json and tsdown.config.ts examples. The workflow includes 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 outputs include .mjs, .cjs, .d.ts). Each step links to the relevant reference file. The workflow is well-sequenced and includes verification of the build output before proceeding to testing and release. | 3 / 3 |
Progressive Disclosure | Excellent progressive disclosure pattern. The main skill is a concise overview (~300 tokens as noted) with well-organized one-level-deep references via both a quick-reference table and a task-based checklist. Explicit instruction to NOT load all files at once. References are clearly signaled with descriptive labels. | 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
48efc7a
- 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.