CtrlK

api-client-generator

Api Client Generator - Auto-activating skill for API Integration. Triggers on: api client generator, api client generator Part of the API Integration skill category.

Install with Tessl CLI

npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill api-client-generator

What are skills?

Overall
score

17%

Review — 0%

Does it follow best practices?

Validation — 11 / 16 Passed

Validation for skill structure

SKILL.md

Review

Evals

Activation

This description is essentially a placeholder with no substantive content. It only provides the skill name and category without describing what the skill actually does, what specific capabilities it offers, or when Claude should select it. The duplicate trigger term suggests auto-generated or incomplete metadata.

Suggestions

Add specific actions the skill performs, e.g., 'Generates client libraries from OpenAPI/Swagger specifications, creates typed SDK wrappers, produces API request/response models'

Add a 'Use when...' clause with natural trigger terms like 'generate API client', 'create SDK', 'OpenAPI spec', 'REST client library', 'API wrapper code'

Include supported formats or languages to distinguish from other API skills, e.g., 'for TypeScript, Python, or Go clients from REST API definitions'

Dimension	Reasoning	Score
Specificity	The description only names the skill ('Api Client Generator') and category ('API Integration') without describing any concrete actions. There are no specific capabilities listed like 'generates client libraries', 'parses OpenAPI specs', or 'creates SDK wrappers'.	1 / 3
Completeness	The description fails to answer both 'what does this do' (no actions described) and 'when should Claude use it' (no 'Use when...' clause or explicit trigger guidance). Only provides category metadata.	1 / 3
Trigger Term Quality	The trigger terms are just the skill name repeated twice ('api client generator, api client generator'). Missing natural user phrases like 'SDK', 'REST client', 'API wrapper', 'generate client code', 'OpenAPI', 'Swagger', etc.	1 / 3
Distinctiveness Conflict Risk	The generic 'API Integration' category and lack of specific triggers means this could easily conflict with other API-related skills. Nothing distinguishes it from skills for API testing, API documentation, or general API work.	1 / 3
	Total	4 / 12 Passed

Implementation

This skill content is essentially a placeholder template with no actual instructional value. It contains only meta-descriptions of what a skill should do without any concrete guidance, code examples, or actionable steps for API client generation. The content would be completely unhelpful for Claude attempting to perform any API client generation task.

Suggestions

Add concrete, executable code examples showing how to generate API clients (e.g., using OpenAPI Generator, swagger-codegen, or manual approaches with specific HTTP libraries)

Define a clear workflow with numbered steps: analyze API spec → choose generation approach → generate client → validate output → handle authentication

Include specific examples of input (API spec snippet) and expected output (generated client code)

Remove all generic boilerplate ('provides automated assistance', 'follows best practices') and replace with actual technical guidance

Dimension	Reasoning	Score
Conciseness	The content is padded with generic boilerplate that explains nothing Claude doesn't already know. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler with zero actionable information.	1 / 3
Actionability	There is no concrete guidance whatsoever—no code, no commands, no specific steps, no examples of actual API client generation. The entire content describes what the skill supposedly does without showing how to do anything.	1 / 3
Workflow Clarity	No workflow is defined. There are no steps, no sequence, no validation checkpoints. The skill claims to provide 'step-by-step guidance' but contains none.	1 / 3
Progressive Disclosure	The content is a monolithic block of vague descriptions with no structure for discovery. No references to detailed documentation, no links to examples or advanced features, no organization beyond generic headings.	1 / 3
	Total	4 / 12 Passed

Validation

69%

Warnings & errors only

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: 23 days ago

Table of Contents

Activation Implementation Validation

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.