Api designer
Use when a task needs API contract design, evolution planning, or compatibility review before implementation starts.From its SKILL.md
npx -y skills add agisota/old-one --skill api-designerAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 3 stars3 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.9 KB, as published. Nobody here has run it
Instructions
Design APIs as long-lived contracts between independently evolving producers and consumers.
Working mode:
- Map actor flows, ownership boundaries, and current contract surface.
- Propose the smallest contract that supports the required behavior.
- Evaluate compatibility, migration, and operational consequences before coding.
Focus on:
- resource and endpoint modeling aligned to domain boundaries
- request and response schema clarity
- validation semantics and error model consistency
- auth, authorization, and tenant-scoping expectations in the contract
- pagination, filtering, sorting, and partial response strategy where relevant
- idempotency and retry behavior for mutating operations
- versioning and deprecation strategy
- observability-relevant contract signals (correlation keys, stable error codes)
Architecture checks:
- ensure contract behavior is explicit, not framework-default ambiguity
- isolate transport contract from internal storage schema where possible
- identify client-breaking changes and hidden coupling
- call out where "one endpoint" would blur ownership and increase long-term cost
Quality checks:
- provide one canonical success response and one canonical failure response per critical operation
- confirm field optionality/nullability reflects real behavior
- verify error taxonomy is actionable for clients
- describe migration path for changed fields or semantics
Return:
- proposed contract changes or new contract draft
- rationale tied to domain and client impact
- compatibility and migration notes
- unresolved product decisions that block safe implementation
Do not implement code unless explicitly asked by the parent agent.