api-design
Use this skill when designing APIs, choosing between REST/GraphQL/gRPC, writing OpenAPI specs, implementing pagination, versioning endpoints, or structuring request/response schemas. Triggers on API design, endpoint naming, HTTP methods, status codes, rate limiting, authentication schemes, HATEOAS, query parameters, and any task requiring API architecture decisions.
npx skills add majiayu000/claude-skill-registry --skill api-design-absolutelyskilled-absolutelyskilled --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
When this skill is activated, always start your first response with the 🧢 emoji. # API Design API design is the practice of defining the contract between a service and its consumers in a way that is consistent, predictable, and resilient to change. A well-designed API reduces integration friction, makes versioning safe, and communicates intent through naming and structure rather than documentation alone. This skill covers the three dominant paradigms - REST, GraphQL, and gRPC - along with OpenAPI specs, pagination strategies, versioning, error formats, and authentication patterns. --- ## When to use this skill Trigger this skill when the user: - Asks how to name, structure, or version API endpoints - Needs to choose between REST, GraphQL, or gRPC for a new service - Wants to write or review an OpenAPI / Swagger specification - Asks about HTTP status codes and when to use each - Needs to implement pagination (offset, cursor, keyset) - Asks about authentication schemes (API key, OAuth2, JWT) - Wants a consistent error response format across their API - Needs to design request/response schemas or query parameters Do NOT trigger this skill for: - Internal function/method interfaces in
- When to use this skill
- Key principles
- Core concepts
- REST resources
- GraphQL schema
- gRPC + Protobuf
- When to use which
- Common tasks
- 1. Design RESTful resource endpoints
- 2. Write an OpenAPI 3.1 spec
- 3. Implement cursor-based pagination
- 4. Implement API versioning
- 5. Design error response format (RFC 7807)
- 6. Design authentication
What does the api-design skill do?
Use this skill when designing APIs, choosing between REST/GraphQL/gRPC, writing OpenAPI specs, implementing pagination, versioning endpoints, or structuring request/response schemas. Triggers on API design, endpoint naming, HTTP methods, status codes, rate limiting, authentication schemes, HATEOAS, query parameters, and any task requiring API architecture decisions.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill api-design-absolutelyskilled-absolutelyskilled --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.