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
Evaluation results
100%
12%Hotel Booking Platform API Design
REST resource URL and status code design
Noun-based URLs
100%
100%
Correct HTTP methods
100%
100%
201 for creation
100%
100%
Location header on create
100%
100%
204 for no-body responses
100%
100%
422 for validation errors
60%
100%
Flat URL structure
50%
100%
Pagination on collections
70%
100%
Query param for filtering/sorting
100%
100%
No 200 for errors
100%
100%
404 for missing resources
100%
100%
90%
Patient Records API — Security Design
API security and authentication
OAuth/JWT recommendation
100%
100%
401 vs 403 distinction
100%
100%
no-store cache header
100%
100%
Rate limiting per client
100%
100%
429 for rate limit exceeded
100%
100%
CORS configuration
100%
100%
HTTPS/TLS required
100%
100%
No sensitive data in URLs
100%
100%
Input validation mentioned
0%
0%
Auth failure codes consistent
100%
100%
92%
25%SaaS Analytics API — Implementation Review
Collection endpoints and input validation
Noun-based routes
0%
100%
Correct method for delete
100%
100%
Correct method for update
100%
100%
Pagination on list endpoints
100%
100%
201 for resource creation
100%
100%
Location header on create
0%
0%
404 not 200 for missing resources
100%
100%
204 for delete
0%
100%
Input validation with 422
41%
100%
CHANGES.md documents REST fixes
100%
100%
- Repository
- NeverSight/skills_feed
- Commit
f772de4
- Evaluated
- Agent
- Claude Code
- Model
- Claude Sonnet 4.6
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.