rest-endpoint-designer

Rest Endpoint Designer - Auto-activating skill for API Development. Triggers on: rest endpoint designer, rest endpoint designer Part of the API Development skill category.

1.00x

Quality

Does it follow best practices?

Impact

100%

1.00x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./planned-skills/generated/15-api-development/rest-endpoint-designer/SKILL.md

Quality

Discovery

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

This description is extremely thin and auto-generated in nature, providing no concrete actions, no meaningful trigger terms, and no explicit 'when to use' guidance. It relies entirely on the skill name and a duplicated trigger phrase, making it nearly useless for skill selection among multiple candidates. It needs a complete rewrite with specific capabilities, natural user keywords, and explicit activation conditions.

Suggestions

Add specific concrete actions such as 'Designs REST API endpoints, defines HTTP methods and routes, generates OpenAPI/Swagger specifications, and structures request/response schemas.'

Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about designing REST APIs, creating endpoints, defining routes, HTTP methods, API schemas, or OpenAPI specs.'

Remove the duplicated trigger term and expand with natural keyword variations users would actually say, such as 'REST API', 'API routes', 'endpoint design', 'HTTP endpoints', 'API paths', 'swagger'.

Dimension	Reasoning	Score
Specificity	The description names a domain ('API Development') and a role ('Rest Endpoint Designer') but lists zero concrete actions. There are no specific capabilities like 'design REST routes', 'generate OpenAPI specs', or 'define request/response schemas'.	1 / 3
Completeness	The 'what' is essentially absent (no concrete actions described) and the 'when' is only a duplicated trigger phrase with no explicit 'Use when...' clause or meaningful guidance on activation conditions.	1 / 3
Trigger Term Quality	The only trigger terms listed are the redundant 'rest endpoint designer, rest endpoint designer'. It misses natural user phrases like 'API endpoint', 'REST API', 'route design', 'HTTP methods', 'OpenAPI', 'swagger', etc.	1 / 3
Distinctiveness Conflict Risk	The term 'Rest Endpoint Designer' is somewhat specific to a niche (REST API design), which provides some distinctiveness, but the lack of concrete actions and the generic 'API Development' category could cause overlap with other API-related skills.	2 / 3
	Total	5 / 12 Passed

Implementation

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

This skill is an empty shell with no actual instructional content. It consists entirely of generic boilerplate that repeats the skill name without providing any actionable guidance on REST endpoint design, API patterns, code examples, or workflows. It fails on every dimension of the rubric.

Suggestions

Add concrete, executable code examples showing REST endpoint design (e.g., route definitions, request/response schemas, authentication middleware) in a specific framework like Express, FastAPI, or Spring Boot.

Define a clear workflow for designing REST endpoints: e.g., 1) Define resource model, 2) Map HTTP methods to CRUD operations, 3) Define request/response schemas, 4) Validate with OpenAPI spec, 5) Implement error handling.

Remove all generic boilerplate ('This skill provides automated assistance...') and replace with specific, actionable REST design patterns such as naming conventions, status code usage, pagination, and versioning.

Add references to supplementary files for advanced topics (e.g., 'See AUTH_PATTERNS.md for authentication strategies' or 'See OPENAPI_GUIDE.md for spec generation').

Dimension	Reasoning	Score
Conciseness	The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats 'rest endpoint designer' excessively, and provides zero actual technical content or instructions.	1 / 3
Actionability	There is no concrete guidance whatsoever—no code, no commands, no specific examples, no API design patterns, no endpoint structures. Every section is vague and abstract, describing rather than instructing.	1 / 3
Workflow Clarity	No workflow, steps, or process is defined. The 'Capabilities' section vaguely mentions 'step-by-step guidance' but never provides any. There are no validation checkpoints or sequences.	1 / 3
Progressive Disclosure	The content is a flat, uninformative page with no references to detailed materials, no links to examples or API design guides, and no meaningful structure beyond generic boilerplate headings.	1 / 3
	Total	4 / 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: b8a3b3e

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.