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.
87
83%
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 well-structured skill description with strong trigger term coverage and clear 'when' guidance via the explicit 'Triggers on:' clause. 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 RESTful endpoint structures'), which slightly reduces specificity.
Suggestions
Replace 'Quick reference for' with specific action verbs describing what the skill does, e.g., 'Recommends HTTP status codes, designs RESTful endpoint structures, advises on API versioning strategies, configures caching headers and rate limiting policies.'
| 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 guidance. | 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
77%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, concise REST API quick reference that makes excellent use of tables for scannable lookup. Its main weakness is that it leans heavily on reference files that don't exist in the bundle, and it lacks executable code examples for the more complex topics it covers (caching headers, rate limiting implementation, error response formatting). For a pure reference skill, it's effective but could be more actionable.
Suggestions
Add concrete, executable examples for caching headers (Cache-Control, ETag) and rate limiting response headers inline, since the referenced files don't exist in the bundle.
Include a small code snippet showing a well-structured error response JSON format, as this is a common actionable need when designing APIs.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section is lean and tabular. No unnecessary explanations of what REST is or how HTTP works—it assumes Claude already knows these concepts and provides only the quick-reference data that's useful to have at hand. | 3 / 3 |
Actionability | The skill provides concrete patterns and examples (URL structures, query parameter formats, status codes), but it's primarily a reference table rather than executable code. There are no runnable code snippets for implementing caching headers, rate limiting, or error responses—areas mentioned in the description. | 2 / 3 |
Workflow Clarity | This is a reference/lookup skill rather than a multi-step workflow skill. For its purpose (quick reference for API design decisions), the single-task nature is unambiguous—look up the right method, status code, or pattern. The 'When to Use' section clearly scopes when to apply the skill. | 3 / 3 |
Progressive Disclosure | The skill references four files under ./references/ for detailed patterns, which is good progressive disclosure structure. However, no bundle files were provided, meaning those references don't actually exist, and the main file could benefit from slightly more actionable content on caching and rate limiting rather than deferring entirely to missing files. | 2 / 3 |
Total | 10 / 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
3ae408c
- 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.