Name: openapi-generator
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

openapi-generator

OpenAPI Generator integration. Manage data, records, and automate workflows. Use when the user wants to interact with OpenAPI Generator data.

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/openapi-generator/SKILL.md

Quality

Content

75%Weight 40%Scale 1-5

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

The body is a strong, executable CLI guide with concrete commands and a clear connection state machine, weakened mainly by a few padded/redundant sections and slightly loose step numbering. It is actionable and well-structured.

Suggestions

Remove the concept-introduction paragraph and the near-empty 'OpenAPI Generator Overview' bullet list; Claude already knows what OpenAPI Generator is.

Merge the redundant 'Popular actions' section into 'Searching for actions' to avoid repeating the action-list command.

Fix the step numbering so '1a/1b' and the referenced 'Step 2' map to clearly labeled headers for an unambiguous sequence.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but includes padding Claude does not need: an intro paragraph defining OpenAPI Generator, a near-empty 'OpenAPI Generator Overview' bullet list, and a redundant 'Popular actions' section that repeats the search command.	3 / 5
Actionability	It provides copy-paste-ready, executable commands for every stage (install, login, connection ensure/get, action list, action run with JSON input, proxy request) plus a complete flags table, covering the common cases.	5 / 5
Workflow Clarity	The connect-to-ready flow is a clear state machine with feedback loops (poll until READY, handle CLIENT_ACTION_REQUIRED, re-poll), but step numbering is loose ('1b', references to a 'Step 2' that is not labeled as such), leaving minor sequence gaps.	4 / 5
Progressive Disclosure	Content is well organized into logical sections in a single file with no bundle files present; minor organization gaps (the empty overview section, the redundant popular-actions block) keep it just below a 5.	4 / 5
	Total	16 / 20 Passed

Description

57%Weight 40%Scale 1-5

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

The description correctly names the tool and includes an explicit 'Use when' trigger, but its capability list is generic Membrane template language rather than OpenAPI Generator-specific actions. It is adequate but would benefit from concrete generation-oriented verbs.

Suggestions

Replace 'Manage data, records, and automate workflows' with OpenAPI Generator-specific actions such as 'generate API client libraries, server stubs, and documentation from an OpenAPI specification'.

Add natural trigger synonyms users actually say, e.g. 'OpenAPI spec, Swagger spec, .yaml/.json spec files, code generation'.

Tighten the 'when' clause to reference generation tasks, e.g. 'Use when the user wants to generate client libraries, server stubs, or docs from an OpenAPI/Swagger spec'.

Dimension	Reasoning	Score
Specificity	The description names the domain ('OpenAPI Generator integration') but the listed actions ('Manage data, records, and automate workflows') are generic Membrane boilerplate rather than concrete OpenAPI Generator capabilities like generating API clients or server stubs.	2 / 5
Completeness	Both 'what' and 'when' are explicitly present, with an explicit 'Use when the user wants to interact with OpenAPI Generator data' trigger; the 'what' is generic which keeps it just below a 5.	4 / 5
Trigger Term Quality	It surfaces the natural tool name 'OpenAPI Generator' in the 'Use when' clause, but misses common variations and synonyms users would say (swagger, spec, .yaml, code generation, client libraries).	3 / 5
Distinctiveness Conflict Risk	The named tool 'OpenAPI Generator' and its data-specific trigger give a distinct niche, though the generic 'Manage data, records, and automate workflows' phrasing risks minor overlap with sibling Membrane integration skills.	4 / 5
	Total	13 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/openapi-generator/SKILL.md
Commit: f484c82

Reviewed: 5 days ago

Table of Contents

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