Agent skill · Backend & API

api-designer

Design RESTful or GraphQL APIs with proper conventions. Creates endpoint specifications, request/response schemas, and documentation. Use when user says 'design API', 'endpoints', 'REST', 'GraphQL', or 'API spec'.

majiayu000github.com/majiayu000GitHub ↗
claude-codecan modify filesMIT
Install
npx skills add majiayu000/claude-skill-registry --skill api-designer-khamel83-oneshot --agent claude-code

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

Facts
Files in the skill folder: 2
SKILL.md size: 7 KB
Bundled scripts: none
Allowed tools: ReadWriteEdit
Path: skills/api/api-designer-khamel83-oneshot/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 You are an expert at designing clean REST and GraphQL APIs. ## When To Use - User says "Design the API", "What endpoints do we need?" - User asks to "Create API spec" - New feature requires API endpoints - Refactoring existing API ## Inputs - Feature requirements - Data models involved - Authentication requirements ## Outputs - API specification (OpenAPI/Swagger or markdown) - Endpoint documentation - Example requests/responses ## REST Conventions | Action | Method | Endpoint | Response | |--------|--------|----------|----------| | List | GET | `/resources` | `200 + []` | | Get one | GET | `/resources/:id` | `200` or `404` | | Create | POST | `/resources` | `201 + object` | | Update | PUT/PATCH | `/resources/:id` | `200 + object` | | Delete | DELETE | `/resources/:id` | `204` or `404` | ## Workflow ### 1. Identify Resources What entities does this feature involve? ### 2. Define Operations CRUD? Custom actions? ### 3. Design URLs - Use nouns, not verbs - Nest appropriately - Plural for collections ### 4. Define Request/Response - Fields, types - Required vs optional - Pagination for lists ### 5. Error Handling Standard error format, appropriate status codes. ### 6. Do

What's inside
Steps it walks through
  1. When To Use
  2. Inputs
  3. Outputs
  4. REST Conventions
  5. Workflow
  6. 1. Identify Resources
  7. 2. Define Operations
  8. 3. Design URLs
  9. 4. Define Request/Response
  10. 5. Error Handling
  11. 6. Document
  12. URL Design
  13. Good
  14. Bad
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
descriptive-statisticsSummarizing and visualizing data through measures of center, spread, shape, and position. Covers…Data & Analyticsperplexity-researcher-reasoning-proHighest level of research and reasoning capabilities for complex decision-making with significant…OtherretroBrutally honest engineering retrospective. Analyzes git history for what actually happened — not…Data & AnalyticsanalyzeUniversal multi-perspective analyzer for any topic, file, idea, or decision. Extract key points…Otherarize-prompt-optimizationINVOKE THIS SKILL when optimizing, improving, or debugging LLM prompts using production trace data…Data & Analyticscellxgene-contextGuide for integrating CellxGene Census single-cell data with ENCODE bulk experiments. Use when…Data & Analytics
About this skill
What does the api-designer skill do?

Design RESTful or GraphQL APIs with proper conventions. Creates endpoint specifications, request/response schemas, and documentation. Use when user says 'design API', 'endpoints', 'REST', 'GraphQL', or 'API spec'.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill api-designer-khamel83-oneshot --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
All skills →
The full catalog, by category and by tool.
Open Source Radar →
The repositories these skills come from, watched daily.
The people behind them →
Makers and builders across the ecosystem.