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 for REST endpoints, handles authentication setup, and produces error-handling boilerplate.'
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 typed wrappers around REST/GraphQL endpoints.'
Include distinguishing details like supported languages, input formats (OpenAPI/Swagger specs), or output types to differentiate from generic API integration skills.
| 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 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 a hollow placeholder with no actual instructional content. It repeatedly references 'sdk wrapper creator' without ever defining what an SDK wrapper is, how to create one, or providing any code, patterns, or concrete guidance. It fails on every dimension of the rubric.
Suggestions
Replace the abstract descriptions with concrete, executable code examples showing how to create an SDK wrapper (e.g., wrapping a REST API with a typed Python/TypeScript client class).
Add a clear multi-step workflow: analyze API spec → generate client class → add authentication → add error handling → validate with tests.
Include at least one complete, copy-paste-ready example of wrapping a real or realistic API endpoint, with input/output examples.
Remove all meta-description sections ('When to Use', 'Example Triggers', 'Capabilities') that describe the skill rather than teaching the task, and replace with actionable technical content.
| 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 rather than instructs, offering nothing executable or copy-paste ready. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequence, no validation checkpoints. The bullet 'Provides step-by-step guidance' is a claim with no actual steps provided. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic block of vague descriptions with no references to detailed files, no structured navigation, and no separation of overview from detailed 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
b8a3b3e
- 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.