generating-api-sdks
Generate client SDKs in multiple languages from OpenAPI specifications. Use when generating client libraries for API consumption. Trigger with phrases like "generate SDK", "create client library", or "build API SDK".
68
62%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/api-development/api-sdk-generator/skills/generating-api-sdks/SKILL.mdQuality
Discovery
89%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 is a solid description with explicit trigger guidance and a clear niche. Its main weakness is that the capability description could be more specific about the concrete actions performed beyond just 'generate' — e.g., what aspects of SDK generation it handles (models, endpoints, authentication, packaging). The trigger terms and completeness are strong.
Suggestions
Expand the capability description with more specific actions, e.g., 'Generate typed models, API client methods, authentication handling, and package configuration from OpenAPI specifications'.
Consider adding supported language examples (e.g., 'Python, TypeScript, Java, Go') to further improve specificity and trigger term coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | It names the domain (client SDKs from OpenAPI specs) and the core action (generate), but doesn't list multiple specific concrete actions like 'generate models, create API methods, produce authentication helpers, build package configuration'. | 2 / 3 |
Completeness | Clearly answers both 'what' (generate client SDKs in multiple languages from OpenAPI specifications) and 'when' (explicit 'Use when' clause and 'Trigger with phrases' providing concrete trigger guidance). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms: 'generate SDK', 'create client library', 'build API SDK', 'OpenAPI specifications', 'client libraries', 'API consumption'. These cover common variations users would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | The combination of OpenAPI specifications, SDK generation, and client libraries creates a very distinct niche that is unlikely to conflict with other skills like general code generation or API documentation. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads more like a high-level project specification than an actionable skill for Claude. While it has decent structure with clear sections, error handling tables, and references to external files, it critically lacks any concrete, executable code or commands — the core instructions are entirely descriptive. The referenced bundle files don't exist, undermining the progressive disclosure structure.
Suggestions
Add concrete, executable code examples for at least one target language — show actual SDK generation commands, template code for the client class, and model generation patterns rather than describing them abstractly.
Include a specific validation checkpoint after SDK generation (e.g., a command to compile/type-check the generated code) and a feedback loop for fixing generation errors before proceeding to testing.
Replace the narrative examples section with actual input (sample OpenAPI spec snippet) and output (generated client code) pairs that Claude can use as templates.
Either provide the referenced bundle files (implementation.md, errors.md, examples.md) or inline the most critical content — currently the references point to nothing.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is moderately verbose with some unnecessary explanation (e.g., the overview paragraph restates what the instructions will cover, and the examples section describes hypothetical outputs rather than showing concrete code). However, it's not egregiously padded and most sections carry useful information. | 2 / 3 |
Actionability | Despite listing 9 steps, the instructions are entirely abstract and descriptive — there are no concrete code snippets, no executable commands, no actual SDK generation code or templates. Phrases like 'Generate typed model classes' and 'Implement authentication handling' describe what to do without showing how. The examples section also describes outputs narratively rather than providing executable code. | 1 / 3 |
Workflow Clarity | The 9 steps provide a reasonable sequence, and the error handling table adds some recovery guidance. However, there are no explicit validation checkpoints between steps — step 1 mentions 'validate the OpenAPI specification' but there's no concrete validation command or feedback loop for verifying generated SDK correctness before proceeding to subsequent steps. | 2 / 3 |
Progressive Disclosure | The skill references external files (implementation.md, errors.md, examples.md) which is good structure, but no bundle files are provided, meaning these references lead nowhere. The main file itself contains a fair amount of content that could benefit from being split (e.g., the detailed error handling table), but the references are at least one-level deep and clearly signaled. | 2 / 3 |
Total | 7 / 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.