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.
34
Quality
3%
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
7%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 severely underdeveloped, essentially just restating the skill name without providing any meaningful information about capabilities or usage triggers. It lacks concrete actions, natural trigger terms, and explicit guidance on when Claude should select this skill. The redundant trigger terms and boilerplate category mention provide no value for skill selection.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates typed client libraries from OpenAPI/Swagger specs, creates HTTP request wrappers, produces SDK code in multiple languages'
Include a 'Use when...' clause with natural trigger terms like 'generate SDK', 'create API client', 'REST client', 'API wrapper', 'client library', 'OpenAPI', 'Swagger'
Remove redundant trigger terms and replace with diverse variations users would naturally say when needing this functionality
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only states 'Api Client Generator' and 'API Integration' without describing any concrete actions. There are no specific capabilities listed like 'generates SDK code', 'creates HTTP request wrappers', or 'produces typed client libraries'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and provides no 'when should Claude use it' guidance. There is no 'Use when...' clause or equivalent explicit trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('api client generator' repeated twice) and overly technical. Missing natural variations users might say like 'SDK', 'REST client', 'generate API wrapper', 'create client library', or 'API bindings'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'API client generator' is somewhat specific to a niche, the vague 'API Integration' category could overlap with other API-related skills. The lack of specific triggers and capabilities makes it harder to distinguish from general API tools. | 2 / 3 |
Total | 5 / 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 describes what an API client generator skill would do without providing any actual guidance, code examples, patterns, or workflows. The content consists entirely of meta-descriptions and trigger phrases rather than teaching Claude how to generate API clients.
Suggestions
Add concrete, executable code examples showing how to generate API clients (e.g., using OpenAPI Generator, creating typed clients from specs)
Define a clear workflow: 1) Parse API spec, 2) Generate client code, 3) Validate output, 4) Handle authentication patterns
Include specific patterns for common scenarios: REST clients, GraphQL clients, handling pagination, retry logic, error handling
Remove all meta-content about 'when to use' and 'example triggers' - replace with actual implementation guidance
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual value. It explains what the skill does in abstract terms without any concrete information Claude doesn't already know. | 1 / 3 |
Actionability | No concrete code, commands, or executable guidance is provided. The entire content describes rather than instructs, with vague phrases like 'provides step-by-step guidance' without actually providing any steps. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill claims to provide 'step-by-step guidance' but contains zero actual steps for generating API clients. | 1 / 3 |
Progressive Disclosure | No structure for discovery or navigation. No references to detailed materials, examples, or related documentation. The content is a flat, uninformative placeholder. | 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
0c08951
- 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.