rest-endpoint-designer
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill rest-endpoint-designerRest Endpoint Designer - Auto-activating skill for API Development. Triggers on: rest endpoint designer, rest endpoint designer Part of the API Development skill category.
Validation
69%| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
Implementation
0%This skill content is essentially a placeholder template with no substantive information. It describes what a REST endpoint designer skill would theoretically do without providing any actual guidance, code examples, design patterns, or actionable instructions. The content fails on all dimensions by being verbose yet empty of useful information.
Suggestions
Add concrete REST endpoint design examples with actual code (e.g., route definitions, HTTP method usage, request/response schemas)
Include specific REST design patterns and best practices (resource naming, status codes, versioning, pagination) with executable examples
Define a clear workflow for designing endpoints: 1) identify resources, 2) define routes, 3) specify request/response formats, 4) validate against OpenAPI spec
Reference related documentation files for advanced topics like authentication patterns, error handling, and API versioning strategies
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing Claude doesn't already know. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler with zero actionable information. | 1 / 3 |
Actionability | There is no concrete guidance whatsoever - no code examples, no specific commands, no actual REST endpoint design patterns. The content describes what the skill supposedly does without providing any executable instructions. | 1 / 3 |
Workflow Clarity | No workflow is defined. The skill claims to provide 'step-by-step guidance' but contains zero actual steps. There are no sequences, validation checkpoints, or processes described. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no references to detailed materials, no links to examples, API patterns, or related documentation. The 'Related Skills' section mentions a category but provides no navigation. | 1 / 3 |
Total | 4 / 12 Passed |
Activation
7%This is a minimal, template-like description that provides almost no useful information for skill selection. It lacks concrete actions, natural trigger terms, and explicit usage guidance. The description appears auto-generated with placeholder content rather than thoughtfully crafted.
Suggestions
Add specific capabilities: 'Designs RESTful API endpoints, generates route structures, creates OpenAPI/Swagger specifications, defines HTTP methods and response schemas'
Include a 'Use when...' clause with natural triggers: 'Use when the user asks about designing APIs, creating endpoints, REST architecture, route planning, or mentions terms like API design, endpoints, routes, HTTP methods'
Remove the duplicate trigger term and expand with variations users would naturally say: 'REST API', 'endpoint design', 'API routes', 'resource URLs', 'API structure'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions - only the name 'Rest Endpoint Designer' and category 'API Development'. There are no specific capabilities listed like 'design endpoints', 'generate OpenAPI specs', or 'create route handlers'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and has no 'Use when...' clause or equivalent guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'rest endpoint designer' repeated twice, which is the skill name itself. Missing natural user terms like 'API', 'routes', 'endpoints', 'REST', 'HTTP methods', 'URL paths', etc. | 1 / 3 |
Distinctiveness Conflict Risk | While 'REST endpoint' is somewhat specific to API design, the lack of detail means it could overlap with general API skills, backend development skills, or documentation skills. The category mention provides some distinction. | 2 / 3 |
Total | 5 / 12 Passed |
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.