tsdown

Use when bundling TypeScript libraries - provides tsdown configuration, dual ESM/CJS output, .d.ts generation, package validation, and plugin authoring

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

100%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.

An exemplary skill body: lean, fully executable quick start, clear structure, and well-signaled progressive disclosure to real reference files. No meaningful weaknesses found across any dimension.

Dimension	Reasoning	Score
Conciseness	The body is lean throughout ('Rolldown + Oxc powered TypeScript bundler. Drop-in tsup replacement.'), assumes Claude's competence, and never explains what TypeScript or bundling is; every token earns its place.	5 / 5
Actionability	Quick Start provides copy-paste-ready, fully executable guidance: an install command, a complete tsdown.config.ts, and build/watch commands covering the common case.	5 / 5
Workflow Clarity	This is a simple single-purpose build skill where the action is unambiguous (install -> config -> run tsdown); the simple-skill exception applies and no destructive/batch validation cap is triggered.	5 / 5
Progressive Disclosure	A clear overview in SKILL.md points to four real one-level-deep reference files via a task-to-file table and an explicit per-file loading checklist with 'DO NOT load all files at once', giving easy navigation.	5 / 5
	Total	20 / 20 Passed

Description

92%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 that clearly states both what the skill does and when to use it, with concrete capabilities and a distinct tsdown-focused niche. The only minor gap is missing common synonyms (build, compile, tsup, publish) in the trigger terms.

Suggestions

Add a couple of natural synonyms users might say, e.g. 'build/compile TypeScript libraries' or 'tsup replacement', to round out trigger-term coverage.

Consider mentioning 'publishing npm packages' in the trigger clause since it appears in the body's When-to-Use list but not in the description.

Dimension	Reasoning	Score
Specificity	The description enumerates five concrete capabilities ('tsdown configuration, dual ESM/CJS output, .d.ts generation, package validation, and plugin authoring'), giving comprehensive coverage rather than vague abstractions.	5 / 5
Completeness	It explicitly answers both 'what' (the five capabilities) and 'when' ('Use when bundling TypeScript libraries') with a concrete trigger phrase, matching the top anchor.	5 / 5
Trigger Term Quality	It includes natural terms a user would say ('bundling TypeScript libraries', 'tsdown', '.d.ts', 'ESM/CJS'), but misses common synonyms like 'build', 'compile', 'tsup', or 'publish' that would push it to comprehensive coverage.	4 / 5
Distinctiveness Conflict Risk	Naming the specific tool 'tsdown' alongside a narrow capability set (dual ESM/CJS, .d.ts, plugin authoring) carves a clear niche with minimal overlap risk against generic bundler skills.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: onmax/nuxt-skills
Path: skills/tsdown/SKILL.md
Commit: 50878f5

Reviewed: 12 days ago

Table of Contents

Discovery Implementation Validation

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.