Favicon of api-design

api-design Skill

AI Agent SkillDesign & MediaPythonOpen source

Guide for designing and documenting RESTful APIs. Use when asked to design an API, create endpoints, or document an API. Published by microsoft in haste.

Decision snapshot

Is this a fit?

Best for

Documentation, Design and media, Includes SKILL.md, Reusable instructions

Works with

Compatibility not yet detected.

Access

Permission behavior not yet detected.

Setup

Copy skill directory

Project health

2 months ago · MIT license

Considerations

No specific cautions were detected. Review the source and requested permissions before installing.

What is api-design Skill?

Guide for designing and documenting RESTful APIs. Use when asked to design an API, create endpoints, or document an API. Published by microsoft in haste. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.

Trust signal
95/100
Maintenance signal
90/100
Adoption signal
41/100

Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.

Key capabilities

  • Includes SKILL.md support
  • Reusable instructions support
  • Documentation
  • Design and media
  • Documentation use cases
  • Design and media use cases

Declared skill metadata

  • Source file: .github/skills/api-design/SKILL.md

These fields retain source and confidence evidence from the indexed SKILL.md.

Compatibility and setup

Copy skill directory
  • Install or run with Copy skill directory

When to use api-design Skill

  • Use it for documentation.
  • Use it for design and media.

Built with

PythonCopy skill directory

Editorial notes

Source

  • Creator: microsoft
  • Repository: microsoft/haste
  • Skill file: .github/skills/api-design/SKILL.md

What it does

Guide for designing and documenting RESTful APIs. Use when asked to design an API, create endpoints, or document an API.

Skill instructions

API Design Overview Standards and patterns for designing consistent, well-documented RESTful APIs. Covers naming, HTTP methods, error handling, status codes, and documentation requirements. Key Concepts Naming Conventions - Plural nouns for resources: /users, /orders, /products - Kebab-case for multi-word: /user-profiles - Nest related resources: /users/{id}/orders - Query params for filtering: /users?role=admin&active=true HTTP Methods | Method | Purpose | Idempotent | Response | |--------|---------|------------|----------| | GET | Read | Yes | 200 + body | | POST | Create | No | 201 + body + Location | | PUT | Replace | Yes | 200 + body | | PATCH | Partial update | No | 200 + body | | DELETE | Remove | Yes | 204 (no body) | Error Response Format json { "error": { "code": "VALIDATIONERROR", "message": "Human-readable description", "details": [ {"field": "email", "message": "Invalid email format"} ] } } Status Codes - 200: Success — 201: Created — 204: No content - 400: Bad request — 4

Verified compatibility and discovery

Frequently asked questions

What is api-design?

api-design is a open-source AI agent skill with Copy skill directory. Guide for designing and documenting RESTful APIs. Use when asked to design an API, create endpoints, or document an API.

Who is api-design best for?

api-design is best for reusing agent instructions, scripts, and references, documentation workflows, design and media workflows.

How do I install api-design?

Install or run api-design using Copy skill directory. Check api-design for the latest setup command.

Is api-design actively maintained?

api-design may need a closer maintenance check before production use.

Share:

Stars
43
Forks
5
Last commit
2 months ago
Last verified
Aug 31, 2026
Metadata fetched
Aug 31, 2026
Repository age
5 months
License
MIT

Project health auto-fetched from the source repository.

Maintain this resource?

Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.

Alternatives to api-design