generating-api-sdks

tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill 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".

51%

Overall

Validation — 81%

Implementation — 7%

Activation — 90%

SKILL.md

Review

Evals

Validation

81%

Warnings & errors only

Criteria	Description	Result
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

	Total	13 / 16 Passed

Implementation

This skill content is a generic template that fails to provide SDK-generation-specific guidance. It conflates API development with SDK generation, contains no executable examples or concrete commands, and the workflow is disorganized with duplicate step numbering. The content would not help Claude generate client SDKs from OpenAPI specifications.

Suggestions

Add concrete code examples showing how to generate SDKs from OpenAPI specs (e.g., using openapi-generator-cli with specific language targets)

Fix the duplicate step numbering and create a clear sequential workflow: 1) Parse OpenAPI spec, 2) Select target language, 3) Generate SDK, 4) Validate output

Remove generic prerequisites and add SDK-specific requirements (e.g., 'OpenAPI spec file in JSON/YAML format', 'openapi-generator installed')

Include validation steps to verify generated SDK compiles and matches the API spec

Dimension	Reasoning	Score
Conciseness	Contains significant padding and generic boilerplate that doesn't add value. Phrases like 'This skill provides automated assistance for api sdk generator tasks' are redundant. Prerequisites list generic development setup rather than SDK-generation-specific requirements.	1 / 3
Actionability	No concrete code examples, no executable commands, no specific SDK generation patterns. Instructions are vague ('Generate boilerplate code using Bash(api:sdk-*)') without showing actual usage. The skill describes rather than instructs.	1 / 3
Workflow Clarity	Steps are poorly organized with duplicate numbering (two separate lists both starting at 1). The workflow conflates API design with SDK generation. No validation checkpoints for generated SDK code, no feedback loops for error recovery.	1 / 3
Progressive Disclosure	References external files appropriately (implementation.md, errors.md, examples.md) with one-level-deep linking. However, the main content is poorly structured and the overview section adds no value beyond repeating the description.	2 / 3
	Total	5 / 12 Passed

Activation

90%

This is a well-structured description with explicit trigger guidance and clear 'when to use' clauses. The main weakness is limited specificity about concrete capabilities beyond the core generation action. The description effectively distinguishes itself from related skills through specific terminology.

Suggestions

Add specific concrete actions like 'supports TypeScript, Python, Go', 'validates OpenAPI specs', or 'generates type-safe models' to improve specificity

Dimension	Reasoning	Score
Specificity	Names the domain (client SDKs, OpenAPI specifications) and the core action (generate), but doesn't list multiple specific concrete actions like supported languages, validation, customization options, or output formats.	2 / 3
Completeness	Clearly answers both what (generate client SDKs from OpenAPI specs) and when (explicit 'Use when' clause plus 'Trigger with phrases' providing concrete examples). Both components are explicitly stated.	3 / 3
Trigger Term Quality	Explicitly lists natural trigger phrases users would say: 'generate SDK', 'create client library', 'build API SDK'. Also includes relevant terms like 'OpenAPI specifications' and 'API consumption' that users might mention.	3 / 3
Distinctiveness Conflict Risk	Clear niche targeting SDK/client library generation from OpenAPI specs. The specific trigger phrases ('generate SDK', 'create client library', 'build API SDK') are distinct and unlikely to conflict with general code generation or API documentation skills.	3 / 3
	Total	11 / 12 Passed

Reviewed

17 days ago

Table of Contents

Validation Implementation Activation

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.