CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

90

1.92x
Quality

87%

Does it follow best practices?

Impact

98%

1.92x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

78%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, token-efficient skill body with good progressive disclosure and a sequenced workflow including a verification checkpoint. Main gaps are the duplicated file listing and the absence of an explicit failure-recovery loop in the workflow.

Suggestions

Consolidate the Quick Reference table and Loading Files checkbox list into a single navigation section to remove the duplicated file directory.

Add an error-recovery step to the New Library Workflow (e.g., 'If the build is missing .d.ts or a format, check tsdown entry/format config and re-run') to turn the verify checkpoint into a full feedback loop.

Inline one or two concrete code snippets for the highest-value tasks (e.g., a minimal dual-export package.json exports map with types) so common cases are actionable without loading a reference.

DimensionReasoningScore

Conciseness

The body is lean with bullet-driven principles and minimal over-explanation, but the file directory is listed twice — once as the Quick Reference table and again as the Loading Files checkbox list with near-identical descriptions — which is redundant and could be trimmed.

4 / 5

Actionability

Provides copy-paste-ready package.json and tsdown.config.ts examples plus a concrete verify command ('pnpm build && pnpm pack --dry-run'), but the inline executable guidance is minimal and leans on reference files for the specifics of each task.

4 / 5

Workflow Clarity

The 'New Library Workflow' gives a clear 6-step sequence with an explicit validation checkpoint (step 4 checks for .mjs/.cjs/.d.ts outputs), but lacks an error-recovery feedback loop describing what to do when verification fails.

4 / 5

Progressive Disclosure

Clear overview with well-signaled one-level-deep references; all 10 referenced files (project-setup, package-exports, build-tooling, etc.) exist in references/ and are organized both as a table and a checklist for easy navigation.

5 / 5

Total

17

/

20

Passed

Description

96%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description with explicit trigger guidance and comprehensive concrete actions. The only minor weakness is slight overlap with general TypeScript/coding skills on API design and type-pattern coverage.

DimensionReasoningScore

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... release workflows' — giving comprehensive coverage rather than vague phrasing.

5 / 5

Completeness

Explicitly answers both what ('covers project setup, package.json exports, build tooling...') and when via two concrete 'Use when' clauses ('Use when authoring TypeScript libraries...', 'Use when bundling, configuring dual CJS/ESM output, or setting up release workflows').

5 / 5

Trigger Term Quality

Includes natural phrases users say ('TypeScript libraries', 'npm packages', 'publishing to npm', 'bundling', 'dual CJS/ESM', 'release workflows') with synonyms (libraries/packages) and tool names (tsdown/unbuild), matching the comprehensive-anchor example.

5 / 5

Distinctiveness Conflict Risk

The library/npm packaging focus (exports, dual CJS/ESM, publishing, release workflows) is a clear niche with minimal conflict; minor overlap risk with general TypeScript skills on 'API design patterns' and 'type inference tricks' keeps it just below 5.

4 / 5

Total

19

/

20

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
onmax/nuxt-skills
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.