api-agent-development-skill
CRITICAL: API agents wrap external HTTP services. They use request/response transforms to adapt between Orchestrator AI''s format and the external service''s format. Status webhook URLs MUST read from environment variables.'
npx skills add majiayu000/claude-skill-registry --skill api-agent-development-skill --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
Guides the creation of API agents that wrap external HTTP services and transform requests and responses to match the Orchestrator AI format. Emphasizes configuring request_transform and response_transform, including a statusWebhook that reads from environment variables, and ensuring A2A protocol compliance.
How it works
- Uses a minimal API agent configuration pattern that forwards a user message through a request_transform template when format is custom. If the template can be parsed as JSON, it is parsed; otherwise the rendered string is sent, defaulting to a body of { prompt: userMessage }.
- Supports a full API agent configuration with fields for endpoint, method, timeout, headers, authentication, request_transform, and response_transform.
- Request transforms provide template variables (e.g., {{userMessage}}, {{sessionId}}, {{conversationId}}, {{taskId}}, {{agentSlug}}, {{organizationSlug}}, {{env.API_BASE_URL}}) and examples show how to construct payloads for external services.
- Response transforms support field_extraction with a dotted/bracket path (e.g., data.answer.text, data.items[0].text) and fallback behavior to stringify non-string results.
- Demonstrates a complete N8N workflow wrapper including how the request body is built and how the response is processed, including status webhook handling via environment variables.
- Includes guidance on correct statusWebhook formatting using {{env.API_BASE_URL}} and fallback options.
When to use it
- Wrapping n8n workflows as API agents
- Wrapping LangGraph/CrewAI/OpenAI endpoints as API agents
- Creating agents that call external HTTP services
- Configuring request/response transformations
- Setting up webhook status tracking
- Ensuring A2A protocol compliance
What it can touch
- Not explicitly enumerated in this summary, but references to API configuration fields (endpoint, method, headers, timeout) and transform templates imply access to the agent runtime to build requests and extract responses.
Caveats
- The material emphasizes environment-based status webhook URLs and JSON-like templates that may be parsed; errors in template rendering fall back to a minimal body.
- It requires adherence to A2A endpoints and .well-known/agent.json structure for protocol compliance.
--- name: API Agent Development description: Create API agents that wrap external HTTP services (n8n, LangGraph, CrewAI, OpenAI endpoints). Configure request/response transforms, webhook status tracking, A2A protocol compliance. CRITICAL: Request transforms use template variables ({{userMessage}}, {{conversationId}}, etc.). Response transforms use field extraction. Status webhook URL must read from environment variables. allowed-tools: Read, Write, Edit, Bash, Grep, Glob --- # API Agent Development Skill **CRITICAL**: API agents wrap external HTTP services. They use request/response transforms to adapt between Orchestrator AI's format and the external service's format. Status webhook URLs MUST read from environment variables. ## When to Use This Skill Use this skill when: - Wrapping n8n workflows as API agents - Wrapping LangGraph/CrewAI/OpenAI endpoints as API agents - Creating agents that call external HTTP services - Configuring request/response transformations - Setting up webhook status tracking - Ensuring A2A protocol compliance ## API Agent Structure API agents wrap external HTTP endpoints and transform requests/responses. They follow this structure: ### Minimal API Agent Co
- When to Use This Skill
- API Agent Structure
- Minimal API Agent Configuration
- Full API Agent Configuration
- Request Transform: Building API Requests
- Template Variables Available
- Request Transform Examples
- Response Transform: Extracting Content
- Field Extraction Pattern
- Response Transform Examples
- Complete Example: N8N Workflow Wrapper
- API Agent Configuration
- How the Request is Built
- How the Response is Handled
What does the api-agent-development-skill skill do?
CRITICAL: API agents wrap external HTTP services. They use request/response transforms to adapt between Orchestrator AI''s format and the external service''s format. Status webhook URLs MUST read from environment variables.'
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill api-agent-development-skill --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.