Agent skill · DevOps & Cloud

api-architect

Expert API designer for REST, GraphQL, gRPC architectures. Activate on: API design, REST API, GraphQL schema, gRPC service, OpenAPI, Swagger, API versioning, endpoint design, rate limiting, OAuth flow. NOT for: database schema (use data-pipeline-engineer), frontend consumption (use web-design-expert), deployment (use devops-automator).'

majiayu000github.com/majiayu000GitHub ↗
claude-codecan modify filesMIT
Install
npx skills add majiayu000/claude-skill-registry --skill api-architect-curiositech-some-claude-skills --agent claude-code

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

Facts
Files in the skill folder: 2
SKILL.md size: 5 KB
Bundled scripts: none
Allowed tools: ReadWriteEditBash(npm:*npx:*openapi-generator:*)
Path: skills/api/api-architect-curiositech-some-claude-skills/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 Architect Expert API designer specializing in REST, GraphQL, gRPC, and WebSocket architectures. ## Activation Triggers **Activate on:** "API design", "REST API", "GraphQL schema", "gRPC service", "OpenAPI", "Swagger", "API versioning", "endpoint design", "rate limiting", "OAuth flow", "API gateway" **NOT for:** Database schema → `data-pipeline-engineer` | Frontend consumption → `web-design-expert` | Deployment → `devops-automator` ## Quick Start 1. **Define API contract first** (API-first design) 2. **Choose paradigm**: REST for CRUD, GraphQL for flexible queries, gRPC for internal services 3. **Write the spec**: OpenAPI for REST, SDL for GraphQL, .proto for gRPC 4. **Design error responses** with consistent structure 5. **Plan versioning** before your first release ## Core Capabilities | Domain | Technologies | |--------|-------------| | **REST** | OpenAPI 3.1, HATEOAS, Pagination | | **GraphQL** | SDL, Relay, DataLoader, Federation | | **gRPC** | Protocol Buffers, Streaming patterns | | **Security** | OAuth 2.0, JWT, API Keys, RBAC | | **DX** | Swagger UI, SDK generation, Sandboxes | ## Architecture Patterns ### API-First Development ``` Design Contract → Generate Stubs → I

What's inside
Steps it walks through
  1. Activation Triggers
  2. Quick Start
  3. Core Capabilities
  4. Architecture Patterns
  5. API-First Development
  6. Response Envelope
  7. Versioning Options
  8. Reference Files
  9. Anti-Patterns (AVOID These)
  10. 1. Verb-Based URLs
  11. 2. Inconsistent Response Envelopes
  12. 3. Breaking Changes Without Versioning
  13. 4. N+1 in GraphQL
  14. 5. Over-fetching REST Endpoints
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the api-architect skill do?

Expert API designer for REST, GraphQL, gRPC architectures. Activate on: API design, REST API, GraphQL schema, gRPC service, OpenAPI, Swagger, API versioning, endpoint design, rate limiting, OAuth flow. NOT for: database schema (use data-pipeline-engineer), frontend consumption (use web-design-expert), deployment (use devops-automator).'

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill api-architect-curiositech-some-claude-skills --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