api-client-generator
Api Client Generator - Auto-activating skill for API Integration. Triggers on: api client generator, api client generator Part of the API Integration skill category.
31
0%
Does it follow best practices?
Impact
87%
1.01xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/16-api-integration/api-client-generator/SKILL.mdQuality
Discovery
0%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is essentially a template placeholder with no substantive content. It fails on all dimensions: it lists no concrete actions, provides no natural trigger terms beyond the skill name repeated, lacks any 'Use when...' guidance, and is too generic to be distinguishable from other API-related skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates typed API client code from OpenAPI/Swagger specifications, creates request/response models, handles authentication setup, and produces SDK wrappers for REST APIs.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to generate an API client, create an SDK, build a REST client wrapper, scaffold HTTP request code, or work with OpenAPI/Swagger specs.'
Remove the duplicate trigger term ('api client generator' listed twice) and expand with natural variations users would actually say, such as 'SDK generator', 'REST client', 'API wrapper', 'HTTP client code', 'OpenAPI codegen'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names a domain ('API Integration') and a tool name ('Api Client Generator') but does not describe any concrete actions. There are no specific capabilities listed like 'generates HTTP client code', 'creates request/response models', or 'parses OpenAPI specs'. | 1 / 3 |
Completeness | The 'what' is extremely vague (no concrete actions described beyond the name) and the 'when' is missing entirely — there is no 'Use when...' clause or equivalent explicit trigger guidance. The description only states it's 'auto-activating' and lists its category. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'api client generator' repeated twice. It misses natural variations users would say like 'generate SDK', 'create API wrapper', 'REST client', 'HTTP client', 'OpenAPI', 'Swagger', 'API bindings', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The description is so generic ('API Integration') that it could easily conflict with any other API-related skill. There are no distinct triggers or specific use cases that would help Claude differentiate this from other API tools. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is a hollow template with no actual instructional content. It repeatedly references 'api client generator' without ever defining what that means, how to do it, or providing any executable code, commands, or concrete guidance. It fails on every dimension of the rubric.
Suggestions
Add concrete, executable code examples showing how to generate an API client (e.g., using OpenAPI Generator, swagger-codegen, or a custom approach with specific commands and configuration files).
Define a clear multi-step workflow: e.g., 1) obtain API spec, 2) validate spec, 3) generate client with specific tool/command, 4) verify generated code compiles/works, with explicit validation checkpoints.
Remove all meta-description sections ('When to Use', 'Example Triggers', 'Capabilities') that describe the skill abstractly and replace them with actual technical instructions, patterns, and examples.
Add references to supplementary files for advanced topics like OAuth integration, webhook handling, or SDK customization patterns, rather than listing them only as tags.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual technical content. Every section restates the same vague information about 'api client generator' without adding substance. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no specific examples, no API patterns, no SDK generation steps. The content only describes what it could do rather than instructing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill claims to provide 'step-by-step guidance' but contains none. There are no validation checkpoints or sequenced operations. | 1 / 3 |
Progressive Disclosure | The content is a flat, repetitive document with no references to detailed materials, no links to examples or advanced guides, and no meaningful structural organization beyond boilerplate headings. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
c8a915c
- 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.