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.
34
0%
Does it follow best practices?
Impact
100%
1.00xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/15-api-development/rest-endpoint-designer/SKILL.mdQuality
Discovery
0%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 essentially a template placeholder with no substantive content. It fails to describe any concrete capabilities, provides only a single duplicated trigger term, lacks a 'Use when...' clause, and is indistinguishable from any other API-related skill. It needs a complete rewrite to be functional.
Suggestions
Add specific concrete actions such as 'Designs RESTful API endpoints, defines URL structures, specifies HTTP methods, and generates request/response schemas including status codes and error handling.'
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 (GET/POST/PUT/DELETE), API schemas, or OpenAPI/Swagger specifications.'
Remove the duplicated trigger term and expand with natural keyword variations users would actually say, such as 'REST API', 'API routes', 'endpoint design', 'resource URLs', 'HTTP verbs', 'API contract'.
| 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 are described. The 'when' is limited to a duplicated trigger phrase with no explicit 'Use when...' clause or meaningful trigger guidance. | 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 'REST API', 'API endpoint', 'route design', 'HTTP methods', 'OpenAPI', 'swagger', or 'API schema'. | 1 / 3 |
Distinctiveness Conflict Risk | The description is so generic ('API Development') that it could easily conflict with any other API-related skill. Nothing distinguishes REST endpoint design from API testing, API documentation, or general API development skills. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%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 template with no substantive content. It contains only generic boilerplate text that repeats the skill name without providing any actual guidance on REST endpoint design, API patterns, code examples, or actionable instructions. It fails on every dimension of the rubric.
Suggestions
Add concrete, executable code examples showing REST endpoint design (e.g., defining routes, request/response schemas, status codes) in a specific framework like Express, FastAPI, or Spring Boot.
Include a clear workflow for designing REST endpoints: identify resources → define URL patterns → choose HTTP methods → define request/response schemas → add validation → document with OpenAPI.
Replace all generic boilerplate sections with actual REST design guidance: naming conventions, HTTP method selection, status code usage, pagination patterns, error response formats, and authentication patterns.
Add specific examples of good vs. bad endpoint design (e.g., 'GET /users/:id' vs 'GET /getUser?id=123') to make the skill immediately actionable.
| 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 domain-specific information or instructions. | 1 / 3 |
Actionability | There is no concrete guidance whatsoever—no code, no commands, no specific API design patterns, no examples of endpoint design. Every section is vague and abstract. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill claims to provide 'step-by-step guidance' but contains none. 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 linked resources, and no meaningful structure beyond generic boilerplate headings. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%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 | |
- Commit
4dee593
- 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.