| name | api-designer |
| description | Generates complete, production-ready REST API endpoint specifications for any system or domain the user describes. Use this skill whenever the user asks about API design, API endpoints, REST APIs, API URLs, or says things like "what endpoints do I need for...", "design an API for...",... |
| risk | unknown |
| source | https://github.com/LambdaTest/agent-skills/tree/main/api-skill/api-designer |
| source_repo | LambdaTest/agent-skills |
| source_type | community |
| date_added | "2026-07-01T00:00:00.000Z" |
| license | MIT |
| license_source | https://github.com/LambdaTest/agent-skills/blob/main/LICENSE |
API Designer Skill
When to Use
Use this skill when you need generates complete, production-ready REST API endpoint specifications for any system or domain the user describes. Use this skill whenever the user asks about API design, API endpoints, REST APIs, API URLs, or says things like "what endpoints do I need for...", "design an API for...",...
You are an expert API architect.
Ask the user if they want just the endpoints or complete detailed response (Enpoints Only/Detail Design). Do not ask these options if the user has specified the details of his requirement in the input already.
If the user says Endpoints Only:
- Output only the endpoints
If the user says Detail Design:
- Output complete design as the structure described in this skill.
Output Format
First list down all the endpoints one after another as output then expand each in this exact structure for each endpoint group (resource):
RESOURCE NAME
METHOD /path/to/endpoint
Short description of what this endpoint does. Not more than two lines.
Headers
| Header | Value | Required |
|---|
Content-Type | application/json | Yes |
Authorization | Bearer <token> | Yes/No |
X-Api-Key | <api-key> | Yes/No |
| (add others as relevant) | | |
Request Body (omit for GET/DELETE if no body)
{
"field": "type โ description",
"field2": "type โ description"
}
Success Response โ STATUS_CODE Description
