CtrlK
BlogDocsLog inGet started
Tessl Logo

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

71

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

87%

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

A concise, well-organized skill body with concrete instruction-style guidance and clean progressive disclosure via real reference files. The main gap is the absence of an explicit validate-and-retry checkpoint in the generation workflow, which is relevant given the skill writes many files.

Suggestions

Add an explicit validation/verification step to the workflow (e.g., 'Run the generated integration tests; fix generated code until all tests pass before declaring completion') so the sequence has a feedback loop.

Consider including at least one small executable code snippet (e.g., a sample route handler or RFC 7807 error envelope) to push actionability toward copy-paste readiness.

Mark step 8 (integration tests) as a checkpoint that gates completion, making the validate-then-proceed intent explicit.

DimensionReasoningScore

Conciseness

The body is lean and structured with no padding or explanation of concepts Claude already knows; prerequisites, instructions, an error table, and examples each earn their tokens and assume Claude's competence.

3 / 3

Actionability

Guidance is concrete and specific — named HTTP methods and route shapes, named validators (Zod/Pydantic/Bean Validation), RFC 7807 envelopes, and defined test coverage areas. Per the rubric's instruction-only scoring note, the absence of code is not penalized because the guidance is actionable.

3 / 3

Workflow Clarity

The nine steps are clearly sequenced, but this file-generating workflow has no explicit validation checkpoint (e.g., run tests and only proceed when passing); the generated tests are produced but never invoked as a feedback loop, so per the rubric's destructive/batch guideline workflow clarity is capped at 2.

2 / 3

Progressive Disclosure

The body is an overview that points to one-level-deep references (implementation.md, errors.md, examples.md), all of which are real files in ./references/, clearly signaled and appropriately split from the main content.

3 / 3

Total

11

/

12

Passed

Description

90%

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 well-structured description that clearly communicates purpose, trigger conditions, and natural keywords in third-person voice. The only weakness is that specificity could enumerate more distinct concrete actions rather than restating the single 'generate implementations' action across two input sources.

DimensionReasoningScore

Specificity

Names the domain (REST APIs from OpenAPI specs or database schemas) and the concrete action of generating implementations, but enumerates essentially one action rather than multiple distinct concrete actions, so it sits at the 'names domain and some actions' level rather than the comprehensive 3-anchor.

2 / 3

Completeness

Explicitly states what it does ('Generate complete REST API implementations from OpenAPI specifications or database schemas') and when to use it ('Use when generating RESTful API implementations') with explicit trigger guidance, satisfying both requirements.

3 / 3

Trigger Term Quality

Provides natural phrases users would say — 'generate REST API', 'create RESTful API', 'build REST endpoints' — alongside 'Use when generating RESTful API implementations', giving good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

The niche (REST API generation from OpenAPI/DB schemas) is clearly bounded with distinct trigger phrases, making it 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.