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 restates the skill name, duplicates the same trigger term, and provides no concrete actions, use cases, or distinguishing details. It would be nearly impossible for Claude to correctly select this skill from a pool of similar skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates typed API client code from OpenAPI/Swagger specs, creates HTTP request wrappers, handles authentication setup, and produces SDK-style interfaces 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 wrapper, scaffold HTTP calls from an OpenAPI spec, or mentions Swagger codegen.'
Diversify trigger terms to include natural user language variations such as 'SDK generator', 'REST client', 'API wrapper', 'OpenAPI', 'Swagger', 'HTTP client library', '.yaml spec'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names a domain ('API Integration') and a tool name ('Api Client Generator') but provides no concrete actions. There is no mention of what the skill actually does—no verbs like 'generates', 'creates', 'parses endpoints', etc. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no explicit 'Use when...' clause, and the 'what' is essentially just the skill name restated without elaboration. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'api client generator' repeated twice. These are not natural phrases users would say; users are more likely to say things like 'generate SDK', 'create API wrapper', 'REST client', 'HTTP client', 'OpenAPI', 'Swagger', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The description is extremely generic—'API Integration' could overlap with many other skills (API testing, API documentation, REST endpoint creation, etc.). There are no distinct triggers or specific capabilities that would differentiate this skill. | 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 an empty placeholder with no actionable content. It consists entirely of generic boilerplate that repeats the phrase 'api client generator' without providing any concrete guidance, code examples, tool references, or workflows for actually generating API clients. It fails on every dimension of the rubric.
Suggestions
Add concrete, executable code examples showing how to generate an API client from an OpenAPI/Swagger spec (e.g., using openapi-generator-cli or similar tools with specific commands).
Define a clear multi-step workflow: e.g., 1) Parse/validate the API spec, 2) Generate client code, 3) Validate generated output, 4) Customize/configure—with explicit validation checkpoints.
Remove all boilerplate text ('This skill provides automated assistance...', 'This skill activates automatically when you...') and replace with lean, actionable instructions that assume Claude's competence.
Add references to supporting files for advanced topics (e.g., authentication patterns, SDK customization templates, language-specific generation configs) to enable progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats the trigger phrase numerous times, and contains zero substantive information about how to actually generate API clients. | 1 / 3 |
Actionability | There is no concrete guidance whatsoever—no code examples, no commands, no specific libraries, no schemas, no API patterns. Every section is vague and descriptive rather than instructive. | 1 / 3 |
Workflow Clarity | No workflow is defined. The skill claims to provide 'step-by-step guidance' but contains zero actual steps, no sequencing, and no validation checkpoints for what is inherently a multi-step code generation task. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no references to supporting files, no structured navigation, and no bundle files to support it. There is nothing to progressively disclose because there is no substantive content. | 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
3a2d27d
- 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.