generating-rest-apis

Generate complete REST API implementations from OpenAPI specifications or database schemas. Use when generating RESTful API implementations. Trigger with phrases like "generate REST API", "create RESTful API", or "build REST endpoints".

Quality

54%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/api-development/rest-api-generator/skills/generating-rest-apis/SKILL.md

Quality

Discovery

67%

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 is structurally sound with explicit 'Use when' and 'Trigger with' clauses, which is good for completeness. However, it lacks specificity about what the generated output includes (e.g., controllers, models, validation, authentication) and could benefit from broader trigger term coverage including common synonyms like 'Swagger' or 'CRUD API'.

Suggestions

Add specific concrete actions describing what the implementation includes, e.g., 'Generates route handlers, request validation, error handling, and CRUD operations from OpenAPI specifications or database schemas'.

Expand trigger terms to include common synonyms and variations users would naturally say, such as 'Swagger spec', 'CRUD API', 'API scaffold', 'API boilerplate', 'web service', or 'API from schema'.

Dimension	Reasoning	Score
Specificity	It names the domain (REST API implementations) and mentions inputs (OpenAPI specifications, database schemas), but doesn't list specific concrete actions beyond 'generate'. It lacks detail on what the implementation includes (e.g., route handlers, validation, middleware, CRUD operations).	2 / 3
Completeness	Clearly answers both 'what' (generate complete REST API implementations from OpenAPI specs or database schemas) and 'when' (explicit 'Use when' clause and 'Trigger with phrases' providing concrete trigger guidance).	3 / 3
Trigger Term Quality	Includes some relevant terms like 'REST API', 'RESTful API', 'REST endpoints', 'OpenAPI specifications', 'database schemas'. However, it misses common variations users might say such as 'API scaffold', 'API boilerplate', 'Swagger', 'CRUD API', 'API from schema', or 'web service endpoints'.	2 / 3
Distinctiveness Conflict Risk	The focus on REST API generation from OpenAPI specs/database schemas is fairly specific, but 'generate REST API' could overlap with general code generation skills or backend development skills. The description doesn't strongly differentiate from broader API or code generation tools.	2 / 3
	Total	9 / 12 Passed

Implementation

42%

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

The skill has good structural organization and progressive disclosure with clear references to supporting files, but critically lacks actionable, executable content. The instructions read as high-level descriptions of what to do rather than concrete guidance with code examples, commands, or templates that Claude could directly execute. The workflow is sequenced but missing validation checkpoints for what is inherently a complex, multi-step generation process.

Suggestions

Add executable code snippets for at least one framework (e.g., a complete Express route file for a CRUD resource) so Claude has a concrete template to follow rather than abstract descriptions.

Include validation checkpoints in the workflow, such as 'Run the test suite after generating routes to verify all endpoints return expected status codes' or 'Validate the generated OpenAPI spec with `npx @redocly/cli lint openapi.yaml`'.

Replace the prose-only examples with at least one concrete input/output pair showing an actual OpenAPI spec snippet and the corresponding generated route code.

Trim the prerequisites section—Claude doesn't need to be told about package managers or HTTP testing tools—and focus that space on actual implementation patterns.

Dimension	Reasoning	Score
Conciseness	The content is moderately efficient but includes unnecessary verbosity in places—the prerequisites section lists many alternatives Claude already knows about, the overview restates what the description already covers, and the examples section describes scenarios without providing executable code. Some tightening is possible.	2 / 3
Actionability	Despite listing 9 steps, the skill provides zero executable code, no concrete commands, no copy-paste-ready snippets, and no actual implementation patterns. Every instruction is abstract ('Create route files implementing...', 'Wire authentication middleware...'). The examples section describes scenarios in prose rather than showing actual code or commands.	1 / 3
Workflow Clarity	Steps are numbered and sequenced logically, but there are no validation checkpoints, no feedback loops for error recovery, and no explicit verification steps between generation phases. For a skill that generates entire API implementations (a complex, multi-step process), the absence of validation gates is a significant gap.	2 / 3
Progressive Disclosure	The skill is well-structured with clear sections and appropriately references external files (implementation.md, errors.md, examples.md) at one level deep with clear signaling. The main file serves as an overview with navigation to detailed materials.	3 / 3
	Total	8 / 12 Passed

Validation

81%

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 — 9 / 11 Passed

Validation for skill structure

Criteria	Description	Result
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	9 / 11 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 70e9fa4

Reviewed: 4 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.