CtrlK
BlogDocsLog inGet started
Tessl Logo

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".

61

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/api-development/api-sdk-generator/skills/generating-api-sdks/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Well-structured content with excellent progressive disclosure and a clean sequenced workflow, but it leans descriptive: instructions lack executable code, and the multi-language generation/publishing pipeline omits an explicit validation checkpoint between generation and release.

Suggestions

Add an explicit validation/test checkpoint in the Instructions (e.g., compile and run the mock-server test suite for each language before bumping versions and publishing) to raise workflow clarity.

Include at least one small executable snippet (e.g., an OpenAPI Generator CLI command or a sample client instantiation) to make the guidance copy-paste ready.

Trim the Prerequisites and Output path lists to essentials, since much of that is derivable, to improve token efficiency.

DimensionReasoningScore

Conciseness

The body assumes Claude's competence with no concept-explaining filler, but several sections (Prerequisites list, Output path listing, Resources) are descriptive rather than tightly instructive and could be trimmed to earn a 3.

2 / 3

Actionability

Steps use specific verbs and named artifacts ("Create a client class with methods...", error table with concrete solutions), but there is no executable code or commands — guidance is concrete yet descriptive rather than copy-paste ready.

2 / 3

Workflow Clarity

The 9-step sequence is clearly ordered, but this multi-language generation/publishing operation lacks an explicit validation checkpoint (e.g., compile/test generated SDKs before publish), which per the guidelines caps workflow clarity at 2 for batch operations.

2 / 3

Progressive Disclosure

SKILL.md is a clear overview with well-signaled, one-level-deep references to implementation.md, errors.md, and examples.md — all real bundle files confirmed to exist — and content is appropriately split.

3 / 3

Total

9

/

12

Passed

Description

90%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that explicitly covers capability, usage timing, and trigger phrases in a concise third-person voice. The only mild gap is specificity, which names one primary action rather than enumerating several concrete actions.

DimensionReasoningScore

Specificity

Names a concrete domain and action ("Generate client SDKs in multiple languages from OpenAPI specifications") but lists only one core action rather than multiple specific concrete actions, matching the score-2 anchor of naming a domain and some actions.

2 / 3

Completeness

Clearly states what it does (generate multi-language SDKs from OpenAPI) and when to use it ("Use when generating client libraries for API consumption" plus explicit trigger phrases), satisfying both halves.

3 / 3

Trigger Term Quality

Explicit natural phrases users would say — "generate SDK", "create client library", "build API SDK" — provide good coverage of natural trigger terms.

3 / 3

Distinctiveness Conflict Risk

The OpenAPI-to-SDK niche with dedicated trigger phrases is clearly distinguishable and unlikely to fire for unrelated skills.

3 / 3

Total

11

/

12

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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

14

/

16

Passed

Repository
jeremylongshore/claude-code-plugins-plus-skills
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.