sdk-wrapper-creator
Sdk Wrapper Creator - Auto-activating skill for API Integration. Triggers on: sdk wrapper creator, sdk wrapper creator Part of the API Integration skill category.
33
0%
Does it follow best practices?
Impact
94%
0.97xAverage 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/sdk-wrapper-creator/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 placeholder with no substantive content. It repeats the skill name as its only trigger term, provides no concrete actions or capabilities, and lacks any explicit guidance on when Claude should select this skill. It would be nearly impossible for Claude to correctly choose this skill from a pool of similar API-related skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates typed SDK wrapper classes from API specifications, creates method signatures from endpoint definitions, handles authentication setup, and produces documentation for the generated SDK.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to wrap an API, create a client library, generate an SDK, build API bindings, or create a typed wrapper around a REST/GraphQL API.'
Expand trigger terms to include natural variations users would say: 'SDK', 'client library', 'API wrapper', 'API client', 'wrapper class', 'OpenAPI', 'REST client', '.swagger'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'SDK Wrapper Creator' is a name, not a description of capabilities. There are no specific actions like 'generates wrapper classes', 'maps API endpoints', or 'creates typed interfaces'. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no explanation of what the skill actually does beyond its name, and no explicit 'Use when...' clause or equivalent trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'sdk wrapper creator' repeated twice. These are not natural keywords users would say — users are more likely to say things like 'wrap this API', 'create an SDK', 'generate client library', or 'API wrapper'. | 1 / 3 |
Distinctiveness Conflict Risk | 'API Integration' is extremely broad and could overlap with many other skills. Without specific capabilities or file types mentioned, this could conflict with any API-related 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 shell with no actual instructional content. It consists entirely of meta-descriptions and placeholder text that repeatedly references 'sdk wrapper creator' without ever providing concrete guidance, code examples, patterns, or actionable steps for creating SDK wrappers. It fails on every dimension of the rubric.
Suggestions
Add concrete, executable code examples showing how to create an SDK wrapper (e.g., wrapping a REST API with a typed Python/TypeScript client class, including authentication, error handling, and retry logic).
Define a clear multi-step workflow for SDK wrapper creation: analyze API spec → generate client class → add auth/error handling → validate against API → write tests.
Remove all meta-description sections ('When to Use', 'Example Triggers', 'Capabilities') that describe the skill abstractly and replace them with actual technical content such as patterns, anti-patterns, and reference examples.
Add references to supplementary files for advanced topics like OAuth flow integration, webhook handling, or SDK generation from OpenAPI specs.
| 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 idea—'sdk wrapper creator'—without adding substance. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no specific patterns, no examples of SDK wrapper creation. The content only describes what the skill would do rather than actually doing or teaching 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 instructions. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic block of vague descriptions 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
4dee593
- 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.