config

How to author a kubb.config.ts and pick the right @kubb/plugin-* packages when generating TypeScript from an OpenAPI/Swagger spec. Use whenever setting up Kubb, adding a generator, or debugging codegen output.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

76%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 tight, highly actionable config skill with an executable example and a complete plugin table. Its main weakness is workflow validation: for a destructive/batch codegen tool, an explicit post-generate verification step and error-recovery loop would lift workflow clarity above the cap of 3.

Suggestions

Add an explicit validation/checkpoint step after `kubb generate` (e.g. typecheck the generated output and confirm expected files exist before wiring into the app), plus an error-recovery loop ('if generate output is missing or malformed, re-run with --verbose, fix the config, and regenerate') to lift workflow_clarity above the destructive/batch cap of 3.

Trim the opening paragraph and the 'What It Does' section, which restate the frontmatter description and 'When to Use'; merging them would push conciseness to 5.

Consider extracting the full per-plugin dependency and option details into a separate reference file linked from the plugins section, which would push progressive_disclosure to 5.

Dimension	Reasoning	Score
Conciseness	Largely lean and efficient (a complete config example, terse 'Rules that matter' bullets, a dense plugin table), but the opening paragraph and 'What It Does' section partly restate the frontmatter description, which could be trimmed.	4 / 5
Actionability	Fully executable: a copy-paste-ready kubb.config.ts, concrete CLI commands (kubb validate, kubb init with --input/--output/--plugins, kubb generate --verbose --watch), and a complete plugin mapping table plus common combinations.	5 / 5
Workflow Clarity	A clear 4-step workflow (validate -> init -> generate -> typecheck) is present with input validation and a typecheck step, but the destructive generate path (output.clean wipes the output dir) lacks an explicit validate-after-generate checkpoint and error-recovery loop; the rubric caps destructive/batch skills missing feedback loops at 3.	3 / 5
Progressive Disclosure	Well-organized sections (When to Use, Shape of a config, Available plugins, Workflow) with clear signaling and a one-level-deep Related Skills pointer; per-plugin Options are deferred to installed type declarations and docs pages, though no separate reference file holds the bulk plugin details.	4 / 5
	Total	16 / 20 Passed

Description

87%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, third-person description that clearly states both what the skill does and when to use it, anchored to tool-specific trigger phrases. Minor room to add a few more natural synonyms, but overall highly specific and distinct.

Dimension	Reasoning	Score
Specificity	Names the domain (authoring kubb.config.ts, picking @kubb/plugin-* packages) and several concrete actions (setting up Kubb, adding a generator, debugging codegen output), with minor gaps in coverage rather than a fully comprehensive action list.	4 / 5
Completeness	Explicitly answers both what ('author a kubb.config.ts and pick the right @kubb/plugin-* packages when generating TypeScript from an OpenAPI/Swagger spec') and when ('Use whenever setting up Kubb, adding a generator, or debugging codegen output') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural user phrasings like 'setting up Kubb', 'adding a generator', 'debugging codegen output' alongside technical terms (TypeScript, OpenAPI/Swagger); a few common synonyms are missing but coverage is strong.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (Kubb codegen config) with distinctive tool-specific triggers (kubb.config.ts, @kubb/plugin-*) that are unlikely to collide with other skills.	5 / 5
	Total	18 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 1 suspicious	Warning

	Total	15 / 16 Passed

Repository: kubb-labs/kubb
Path: tools/claude/skills/config/SKILL.md
Commit: 1bbf973

Reviewed: about 18 hours 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.