sdk-wrapper-creator
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill sdk-wrapper-creatorSdk Wrapper Creator - Auto-activating skill for API Integration. Triggers on: sdk wrapper creator, sdk wrapper creator Part of the API Integration skill category.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This is a very weak skill description that appears to be auto-generated boilerplate with minimal customization. It lacks any concrete actions, meaningful trigger terms, or guidance on when to use the skill. The description would be nearly useless for Claude to distinguish this skill from others in a large skill library.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates typed SDK wrappers from OpenAPI specs, creates client libraries with authentication handling, builds API bindings with error handling and retry logic'
Add a 'Use when...' clause with natural trigger terms like 'Use when the user wants to create an API client, generate SDK code, wrap a REST API, or build a client library from API documentation'
Include file types and technologies involved, e.g., 'OpenAPI, Swagger, REST APIs, TypeScript/Python clients, .yaml, .json specs'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions - only the name 'Sdk Wrapper Creator' and category 'API Integration'. There's no explanation of what creating an SDK wrapper actually involves or what specific tasks it performs. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and has no 'Use when...' clause or equivalent guidance for when Claude should select this skill. Both what and when are essentially missing. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('sdk wrapper creator, sdk wrapper creator'). Missing natural variations users might say like 'API client', 'library wrapper', 'SDK generation', 'API binding', or 'client library'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'SDK wrapper' is somewhat specific terminology, the vague 'API Integration' category and lack of detail means it could overlap with other API-related skills. The repeated trigger term provides minimal differentiation. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill content is essentially a placeholder template with no substantive information about SDK wrapper creation. It describes what the skill claims to do rather than providing any actual guidance, code examples, or actionable instructions. The content would be completely unhelpful for anyone trying to create an SDK wrapper.
Suggestions
Add concrete, executable code examples showing how to create an SDK wrapper (e.g., wrapping a REST API with typed methods, handling authentication, error handling patterns)
Define a clear workflow with steps: analyze API spec → generate client structure → implement methods → add error handling → validate → test
Include specific patterns for common SDK wrapper tasks: request/response typing, rate limiting, retry logic, authentication flows
Reference or link to detailed materials for advanced topics like OAuth integration, webhook handling, or SDK generation tools
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic filler text that provides no actual information about SDK wrapper creation. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless without specifics. | 1 / 3 |
Actionability | Contains zero concrete guidance, no code examples, no commands, and no specific instructions. The 'Example Triggers' section just shows how to ask for help rather than how to actually create SDK wrappers. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. The skill claims to provide 'step-by-step guidance' but contains no actual steps, sequences, or validation checkpoints for SDK wrapper creation. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no references to detailed materials, no links to examples, and no structured navigation to deeper content. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
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.