output

Import and use Kubb's generated code (types, clients, hooks, schemas, mocks). Use when writing app or test code that consumes a Kubb build.

Quality

83%

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

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 lean, well-organized skill body that gives concrete discovery guidance and clear rules for keeping generated code in sync. It would benefit from a copy-paste import example and an explicit typecheck-failure recovery step.

Suggestions

Add a short copy-paste import example showing both barrel and direct-file imports (e.g. `import { useGetPets } from './gen/hooks'`) to lift actionability to fully executable.

Turn the 'Typecheck after regenerating' rule into an explicit feedback loop: 'If typecheck fails, fix the call site or update the spec/config and rerun kubb generate'.

Drop or fold the 'What It Does' section, since its bullets restate 'Where output lands', 'Find what was generated', and 'Rules' that follow it.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and assumes competence (no preamble about what Kubb or OpenAPI is), but the 'What It Does' section restates the rest of the body in a meta, descriptive voice that could be trimmed.	4 / 5
Actionability	Gives concrete, executable guidance (specific paths like 'node_modules/@kubb/plugin-<name>/src/types.ts', the 'kubb generate' command, barrel-vs-direct import rule), but provides no copy-paste import code snippets to anchor the common cases.	4 / 5
Workflow Clarity	The 'Find what was generated' section is a clear 3-step sequence and the Rules include a typecheck validation checkpoint after regenerating, but there is no explicit error-recovery feedback loop.	4 / 5
Progressive Disclosure	A compact, well-sectioned overview (no bundle files exist) with clearly signaled one-level-deep navigation only via the Related Skills table, so structure is appropriate and easy to navigate.	5 / 5
	Total	17 / 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 concise, well-targeted description that explicitly covers both what the skill does and when to use it, anchored to a specific tool. It is distinct and complete, with only minor room to broaden trigger synonyms.

Dimension	Reasoning	Score
Specificity	Names the domain and enumerates five concrete artifact types ('types, clients, hooks, schemas, mocks'), but the actual verbs are limited to 'Import and use', so coverage of distinct actions is not fully comprehensive.	4 / 5
Completeness	Clearly states what it does ('Import and use Kubb's generated code (types, clients, hooks, schemas, mocks)') and gives an explicit, specific 'Use when writing app or test code that consumes a Kubb build' trigger.	5 / 5
Trigger Term Quality	Good natural keyword coverage ('Kubb', 'generated code', 'app or test code', 'Kubb build') with an explicit trigger, but lacks synonyms or file extensions like .ts or kubb.config.ts.	4 / 5
Distinctiveness Conflict Risk	Scoped to a specific tool (Kubb) and its generated artifacts, giving it a clear niche with distinct triggers and minimal overlap 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/output/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.