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

66

Quality

81%

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

SKILL.md
Quality
Evals
Security

Quality

Content

72%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.

A well-organized, token-efficient skill body with clean progressive disclosure into real reference files. It loses points for lacking executable code/commands and for a multi-step generation workflow that omits validation checkpoints.

Suggestions

Add at least one executable code or command snippet (e.g., a sample route handler or a curl test for a generated endpoint) to lift actionability.

Insert explicit validation checkpoints into the workflow, such as 'run the generated integration tests' and 'validate the produced openapi.yaml against the OpenAPI 3.0 schema before finishing'.

Include a brief feedback loop for the destructive/batch steps (e.g., re-run tests after wiring auth middleware) to support error recovery.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence: it does not explain what REST or OpenAPI is, and every section (prerequisites, numbered steps, error table, examples) earns its place.

3 / 3

Actionability

Steps name concrete artifacts (the five REST operations with paths, RFC 7807 envelopes, Zod/Pydantic validators) but provide no executable code or commands, so guidance describes rather than giving copy-paste-ready instruction.

2 / 3

Workflow Clarity

The nine steps are clearly sequenced, but there are no validation checkpoints or feedback loops (e.g., verify the spec validates, run the generated tests, confirm endpoints compile), which caps a multi-step generation workflow at 2.

2 / 3

Progressive Disclosure

The SKILL.md is a concise overview with three real one-level-deep references (implementation.md, errors.md, examples.md), each clearly signaled with 'See ... for ...' and verified to exist in the bundle.

3 / 3

Total

10

/

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, well-structured description that clearly states what it does and when to use it with natural trigger phrases. Its only weakness is that the capability description is somewhat general rather than enumerating multiple concrete actions.

Suggestions

Expand the opening sentence to list several concrete actions (e.g., scaffold CRUD endpoints, add pagination/filtering, generate error envelopes) rather than the single verb 'generate'.

DimensionReasoningScore

Specificity

It names the domain (REST API implementations) and inputs (OpenAPI specs, database schemas) with the action 'generate', but stops short of listing multiple distinct concrete actions as the level-3 anchor requires.

2 / 3

Completeness

It answers both 'what' (generate complete REST API implementations) and 'when' with an explicit 'Use when' clause plus trigger phrases, matching the level-3 anchor.

3 / 3

Trigger Term Quality

Phrases like 'generate REST API', 'create RESTful API', and 'build REST endpoints' are natural terms a user would say, with good variation coverage.

3 / 3

Distinctiveness Conflict Risk

REST API generation from specs/schemas is a clear niche with specific triggers, 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.