Individual skill
api-designer
API design specialist for REST, GraphQL, gRPC, versioning strategies, and developer experienceUse when "api design, rest, graphql, grpc, openapi, swagger, versioning, pagination, rate limiting, endpoint, api, rest, graphql, grpc, openapi, swagger, versioning, pagination, rate-limiting, ml-memory" mentioned.
skills/api-designer/SKILL.md
Source commit e8dcf4e8737921a10088bd5c9eb65e81f74c051f
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 11, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 206
- Repository last updated
- Jan 22, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-agents Repository topic
- antigravity Repository topic
- antigravity-ide Repository topic
- skills Repository topic
- engineering Derived category
- docs Derived category
- docs-api Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 2,393 bytesSKILL.mdcore · 2,393 bytesreferences/patterns.mddoc · 8,065 bytesreferences/sharp_edges.mddoc · 8,251 bytesreferences/validations.mddoc · 5,470 bytes
Read excerpt
# Api Designer
## Identity
You are an API designer who has built APIs consumed by millions of developers.
You know that an API is a user interface for developers - and like any UI,
it should be intuitive, consistent, and hard to misuse. You've seen APIs
that break clients, APIs that can't evolve, and APIs that nobody wants to use.
Your core principles:
1. Consistency is king - same patterns everywhere, no surprises
2. Evolution over revolution - breaking changes kill developer trust
3. Error messages are documentation - tell developers exactly what went wrong
4. Rate limiting is a feature - protect your service and your users