rest-patterns
Quick reference for RESTful API design patterns, HTTP semantics, caching, and rate limiting. Triggers on: rest api, http methods, status codes, api design, endpoint design, api versioning, rate limiting, caching headers.
90
87%
Does it follow best practices?
Impact
94%
1.16xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
89%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 is a solid skill description with excellent trigger term coverage and clear completeness. Its main weakness is that it describes itself as a 'quick reference' rather than listing specific concrete actions (e.g., 'recommends appropriate HTTP status codes, designs endpoint naming conventions, configures caching headers'). The explicit trigger list is a strong feature that aids skill selection.
Suggestions
Replace 'Quick reference for' with specific action verbs describing what the skill does, e.g., 'Recommends HTTP status codes, designs RESTful endpoint structures, configures caching headers, and implements rate limiting strategies.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (RESTful API design) and lists several topic areas (HTTP semantics, caching, rate limiting), but describes itself as a 'quick reference' rather than listing specific concrete actions it performs. | 2 / 3 |
Completeness | Clearly answers both 'what' (quick reference for RESTful API design patterns, HTTP semantics, caching, rate limiting) and 'when' (explicit 'Triggers on:' clause with specific trigger terms), satisfying the requirement for explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'rest api', 'http methods', 'status codes', 'api design', 'endpoint design', 'api versioning', 'rate limiting', 'caching headers' — these are all terms users would naturally use when seeking this kind of help. | 3 / 3 |
Distinctiveness Conflict Risk | The combination of REST API design patterns, HTTP semantics, caching, and rate limiting creates a clear niche. The specific trigger terms like 'status codes', 'endpoint design', and 'api versioning' make it unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured quick-reference skill that excels at conciseness and progressive disclosure. The tables are clean and information-dense. The main weakness is that it leans more toward a lookup reference than actionable guidance—it could benefit from a few concrete code snippets showing implementation of caching headers, rate limiting responses, or error response formats rather than just listing patterns.
Suggestions
Add a concrete example showing a complete request/response pair (e.g., a POST creating a resource with the 201 response including Location header and response body)
Include an executable example for caching headers (e.g., actual Cache-Control header values for common scenarios) rather than deferring entirely to the reference file
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section is a compact table or checklist with no unnecessary explanation. Claude already knows REST concepts, and this skill correctly serves as a quick-reference rather than a tutorial. The 'When to Use' section is slightly redundant but minimal. | 3 / 3 |
Actionability | The skill provides useful reference tables and URL patterns, but lacks executable code examples (e.g., actual request/response examples, caching header configurations, rate limiting implementation). It describes patterns rather than providing copy-paste ready implementations for tasks like setting up caching headers or rate limiting. | 2 / 3 |
Workflow Clarity | This is a reference/lookup skill rather than a multi-step workflow skill. The single-purpose nature (quick reference lookup) is unambiguous, and the content is clearly organized by topic. No destructive or batch operations are involved, so validation checkpoints are not needed. | 3 / 3 |
Progressive Disclosure | Excellent structure: concise overview tables in the main file with clearly signaled one-level-deep references to detailed materials (status-codes.md, caching-patterns.md, rate-limiting.md, response-formats.md). Navigation is straightforward. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- NeverSight/skills_feed
- Commit
f772de4
- 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.