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, includes explicit 'Use when' guidance, and is distinctive enough to avoid conflicts with general TypeScript or web development 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 serves as a well-structured hub for TypeScript library development. It maximizes token efficiency by keeping the main file as a concise overview with actionable quick-start examples while delegating detailed content to clearly referenced files. The workflow includes validation steps, the guidance is concrete and executable, and the progressive disclosure pattern is textbook quality.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient. It assumes Claude's competence with TypeScript, doesn't explain basic concepts, and every section serves a clear purpose. The quick reference table, checklist, and minimal code examples are all high-signal. The token budget note at the bottom is a nice touch. | 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 ('.mjs, .cjs, .d.ts'). 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: pnpm build && pnpm pack --dry-run — check output includes .mjs, .cjs, .d.ts'). Each step links to the relevant reference file, making the process unambiguous. | 3 / 3 |
Progressive Disclosure | Excellent progressive disclosure with a quick reference table, a checklist for loading files, and explicit instruction to NOT load all files at once. References are all one level deep, clearly signaled, and organized by task. The main skill stays concise while pointing to 10 detailed reference files. | 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
- popey/nuxt-skills
- Commit
6b12458
- 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.