ts-sdk-author

Design, build, verify, and publish production-grade TypeScript SDKs as npm packages inside a pnpm monorepo. Covers workspace layout, public API and module boundaries, plugin extension points, branded types and library-tuned tsconfig, tsdown bundling (vs tsup/tsc-only/unbuild), package.json exports with dual ESM+CJS and isomorphic conditions (browser/workers/RN/deno), Turborepo pipelines, publint and @arethetypeswrong/cli verification, changesets pre-release mode, npm dist-tags (latest/next/beta/rc/canary), and the alpha→beta→rc→stable release lifecycle. Triggers on: build a TS SDK, extract core library, package.json exports, dual ESM CJS, tsdown config, tsup vs tsdown, publint, attw, changesets prerelease, npm dist-tag, beta to rc, canary release, pnpm workspace SDK, isomorphic SDK, tsconfig library, npm provenance, shipping a TypeScript library.

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

92%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 strong, executable workflow that moves from workspace skeleton through release lifecycle with concrete configs and commands, explicit verification gates, and well-structured one-level-deep references. Its only weakness is mild verbosity and some redundancy between the phase narrative and the checklist/mistakes tables.

Suggestions

Trim redundancy between the phase invariants and the Pre-Publish Checklist / Common Mistakes tables — reference one from the other rather than restating the same rules (e.g., the 'types first, default last' rule appears in Phase 4, the checklist, and the mistakes table).

Consider collapsing the four Quick Reference tables (File/Field, Bundler, Module-Format, Release Tag) into a single condensed table or moving them into a reference file, since they largely restate decisions already covered in the phases.

Dimension	Reasoning	Score
Conciseness	The body is dense and mostly assumes Claude's competence — verbatim configs, invariants, and command sequences rather than basic explanations — but at ~600 lines it carries some redundancy (e.g., the Pre-Publish Checklist and Common Mistakes table restate invariants already in the phases), keeping it just short of the lean 5-anchor.	4 / 5
Actionability	Fully copy-paste-ready guidance throughout — a complete tsconfig.build.json, tsdown.config.ts, dual-exports package.json, turbo.json, and exact publint/attw/changesets/npm commands — covering the common SDK-authoring cases concretely rather than with pseudocode.	5 / 5
Workflow Clarity	Seven explicitly sequenced phases with a stated dependency warning, a dedicated verification phase (publint + attw + tarball smoke test) wired into a gated prepublishOnly, and a Pre-Publish Checklist serving as a checkpoint list for the complex release process.	5 / 5
Progressive Disclosure	A clear overview file with well-signaled, one-level-deep references — each phase ends with a 'Read next: references/<file>.md — §N …' pointer, all seven referenced files exist on disk, and a closing Reference Files table maps each file to its use-when scenario.	5 / 5
	Total	19 / 20 Passed

Description

100%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 highly specific, third-person description that crisply states what the skill does and gives an explicit trigger clause rich with natural synonyms and tool names. It comprehensively covers both capability and activation conditions with minimal conflict risk.

Dimension	Reasoning	Score
Specificity	Lists many specific concrete actions — 'Design, build, verify, and publish production-grade TypeScript SDKs', workspace layout, branded types, tsdown bundling, dual ESM+CJS exports, isomorphic conditions, Turborepo pipelines, publint/attw verification, changesets pre-release mode, npm dist-tags, and the release lifecycle — giving comprehensive coverage rather than vague abstraction.	5 / 5
Completeness	It explicitly answers both 'what' (design/build/verify/publish TS SDKs in a pnpm monorepo with enumerated subsystems) and 'when' (a dedicated 'Triggers on:' clause with concrete trigger phrases), satisfying the top anchor.	5 / 5
Trigger Term Quality	The explicit 'Triggers on:' clause enumerates natural user phrases including synonyms and tool names — 'build a TS SDK', 'tsup vs tsdown', 'publint', 'attw', 'beta to rc', 'canary release', 'npm dist-tag', 'pnpm workspace SDK', 'npm provenance', 'shipping a TypeScript library' — covering the terms a user would actually say.	5 / 5
Distinctiveness Conflict Risk	The niche is sharply defined — TypeScript SDK authoring in a pnpm monorepo with tsdown, dual ESM+CJS exports, changesets and dist-tag lifecycle — with distinct triggers that are unlikely to fire for unrelated skills.	5 / 5
	Total	20 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (603 lines); consider splitting into references/ and linking	Warning
metadata_field	'metadata' should map string keys to string values	Warning

	Total	14 / 16 Passed

Repository: mindfold-ai/Trellis
Path: .agents/skills/ts-sdk-author/SKILL.md
Commit: 64e6636

Reviewed: 5 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.