Agent skill · Backend & API

api-designer

Design and document RESTful and GraphQL APIs with OpenAPI/Swagger specifications, authentication patterns, versioning strategies, and best practices. Use for: (1) Creating API specifications, (2) Designing REST endpoints, (3) GraphQL schema design, (4) API authentication and authorization, (5) API versioning strategies, (6) Documentation generation

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill api-designer-autumnsgrove-claudeskills --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 14 KB
Bundled scripts: none
Path: skills/api/api-designer-autumnsgrove-claudeskills/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# API Designer ## Overview This skill provides comprehensive guidance for designing, documenting, and implementing modern APIs. It covers both REST and GraphQL paradigms, with emphasis on industry best practices, clear documentation, and maintainable architecture. Use this skill to create production-ready API designs that are scalable, secure, and developer-friendly. ## Core Capabilities ### REST API Design - Resource-oriented endpoint design with proper URL structure - HTTP method semantics and status code usage - Request/response payload design with consistent naming - Pagination, filtering, and sorting strategies - Error handling and validation patterns ### GraphQL API Design - Schema definition with type system and relationships - Query and mutation design with proper input types - Resolver patterns and performance optimization - Fragment usage and directive implementation - N+1 problem prevention strategies ### API Documentation - OpenAPI 3.0 specification generation - Interactive documentation with Swagger UI - Authentication and authorization documentation - Example requests/responses with multiple scenarios - Code generation from specifications ### Authentication & Authoriz

What's inside
Steps it walks through
  1. Overview
  2. Core Capabilities
  3. REST API Design
  4. GraphQL API Design
  5. API Documentation
  6. Authentication & Authorization
  7. API Versioning
  8. When to Use This Skill
  9. REST API Design Workflow
  10. Step 1: Identify Resources
  11. Step 2: Design URL Structure
  12. Step 3: Choose HTTP Methods
  13. Step 4: Design Request/Response Payloads
  14. Step 5: Implement Error Handling
Ships with 1 file
  • metadata.json
Commands it runs
Generate OpenAPI spec from code
python scripts/api_helper.py generate --input api.py --output openapi.yaml
Validate existing spec
python scripts/api_helper.py validate --spec openapi.yaml
Generate documentation site
python scripts/api_helper.py docs --spec openapi.yaml --output docs/
More from claude-skill-registry
All skills →
About this skill
What does the api-designer skill do?

Design and document RESTful and GraphQL APIs with OpenAPI/Swagger specifications, authentication patterns, versioning strategies, and best practices. Use for: (1) Creating API specifications, (2) Designing REST endpoints, (3) GraphQL schema design, (4) API authentication and authorization, (5) API versioning strategies, (6) Documentation generation

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill api-designer-autumnsgrove-claudeskills --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.

Keep going