Api design
Design or review HTTP APIs for resource shape, versioning, authentication, authorization, errors, pagination, idempotency, caching, and evolvability. Use when adding or changing an HTTP surface.From its SKILL.md
npx -y skills add kevinb361/agent-skills --skill api-designAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.2 KB, 186 tokens by cl100k_base, as published. Nobody here has run it
HTTP API design
Start with consumers, operations, trust boundaries, and compatibility constraints. Define resources and behavior before endpoint syntax.
Cover the relevant contract:
- methods, paths, status codes, and content types
- request and response schemas
- validation and stable error shape
- authentication and per-resource authorization
- pagination, filtering, sorting, and bounded limits
- idempotency and retry behavior
- concurrency controls and conditional requests
- caching and rate limits
- observability without secret leakage
- versioning, deprecation, and migration
Prefer boring HTTP semantics and explicit limits. Avoid action-heavy endpoint collections when a resource model is clearer. Distinguish absent, empty, unauthorized, forbidden, conflicted, and temporarily unavailable states.
For a review, cite concrete contract defects and compatibility risks. For a new design, include representative requests, responses, errors, and the decisions consumers must rely on.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.