api-design
REST API design patterns including resource naming, status codes, pagination, filtering, error responses, versioning, and rate limiting for production APIs.
75
66%
Does it follow best practices?
Impact
94%
1.30xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/api-design/SKILL.mdEvaluation results
100%
23%Marketplace Product Catalog API
Response format and status codes
Success data wrapper
100%
100%
POST returns 201
100%
100%
Location header on create
0%
100%
DELETE returns 204
0%
100%
Validation error code
100%
100%
Error code field
100%
100%
Error message field
100%
100%
Field-level validation details
100%
100%
Conflict returns 409
100%
100%
No internal details in errors
50%
100%
Schema-based validation
100%
100%
84%
44%Event Analytics Feed API
Pagination and query parameters
Cursor pagination chosen
50%
100%
N+1 fetch for has_next
0%
60%
has_next in meta
100%
100%
next_cursor in meta
100%
100%
Data wrapper on collection
100%
100%
Bracket notation for comparisons
0%
0%
Comma-separated multi-value
0%
100%
Sort descending prefix
0%
100%
Search uses q param
0%
100%
Sparse fieldsets
50%
100%
100%
TechFlow Public API Design
URL conventions, versioning and rate limiting
Plural resource names
100%
100%
Kebab-case multi-word
100%
100%
No verbs in resource paths
100%
100%
Actions use POST verb endpoint
100%
100%
Nested resources for ownership
100%
100%
URL path versioning
100%
100%
X-RateLimit-Limit header
100%
100%
X-RateLimit-Remaining header
100%
100%
X-RateLimit-Reset header
100%
100%
429 with Retry-After
100%
100%
Sunset header for deprecation
100%
100%
- Repository
- affaan-m/everything-claude-code
- Commit
5df943e
- Evaluated
- Agent
- Claude Code
- Model
- Claude Sonnet 4.6
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.