Understanding APIs and building/maintaining SDKs for developer experience
Generates production-ready SDKs and API documentation for any language. Claude will use this when you need to create client libraries, API reference docs, or code samples that match REST best practices and idiomatic patterns.
/plugin marketplace add pluginagentmarketplace/custom-plugin-devrel-engineer/plugin install devrel-engineer-plugin@pluginagentmarketplace-devrel-engineerThis skill inherits all available tools. When active, it can use any tool Claude has access to.
assets/sdk-design-patterns.yamlreferences/SDK_GUIDE.mdscripts/sdk_validator.pyMaster API design and SDK development to improve developer experience.
parameters:
required:
- artifact_type: enum[api_docs, sdk, code_sample, reference]
- language: string
optional:
- api_spec: object
- version: string
output:
deliverable:
code: string
documentation: markdown
tests: array[TestCase]
GET /users # List users
GET /users/:id # Get single user
POST /users # Create user
PUT /users/:id # Update user (full)
PATCH /users/:id # Update user (partial)
DELETE /users/:id # Delete user
| Code | Meaning | Use When |
|---|---|---|
| 200 | OK | Successful GET/PUT/PATCH |
| 201 | Created | Successful POST |
| 204 | No Content | Successful DELETE |
| 400 | Bad Request | Invalid input |
| 401 | Unauthorized | Missing/invalid auth |
| 403 | Forbidden | Insufficient permissions |
| 404 | Not Found | Resource doesn't exist |
| 429 | Too Many Requests | Rate limit exceeded |
| 500 | Server Error | Something broke |
# Python SDK - Pythonic
client = AcmeClient(api_key="...")
users = client.users.list(limit=10)
# JavaScript SDK - Modern JS
const client = new AcmeClient({ apiKey: "..." });
const users = await client.users.list({ limit: 10 });
SDK
├── Authentication handling
├── Request/response serialization
├── Error handling
├── Pagination helpers
├── Rate limit handling
├── Retry logic
├── Logging/debugging
└── Type definitions
| Section | Purpose |
|---|---|
| Quickstart | First API call in 5 min |
| Authentication | How to authenticate |
| Endpoints | Complete reference |
| Errors | Error codes and handling |
| Rate limits | Usage limits |
| Changelog | Version history |
## Get User
`GET /users/:id`
Returns a user by their ID.
### Parameters
| Name | Type | Required | Description |
|------|------|----------|-------------|
| id | string | Yes | The user ID |
### Response
```json
{
"id": "usr_123",
"email": "user@example.com",
"name": "Jane Doe"
}
404 - User not found401 - Invalid API key
## DevRel API Responsibilities
- Advocate for developer-friendly design
- Create and maintain SDKs
- Write API documentation
- Gather feedback on DX issues
- Support developers using APIs
## Retry Logic
```yaml
retry_patterns:
api_error_500:
strategy: "Exponential backoff with jitter"
max_retries: 3
rate_limit_429:
strategy: "Wait for retry-after header"
fallback: "Exponential backoff"
timeout:
strategy: "Retry with increased timeout"
fallback: "Return partial data"
| Failure Mode | Detection | Recovery |
|---|---|---|
| API breaking change | Tests fail | Update SDK, notify users |
| SDK version mismatch | Compatibility errors | Align versions |
| Missing docs | Support tickets | Add documentation |
□ API spec up to date?
□ SDK matches API version?
□ Error handling complete?
□ Rate limiting documented?
□ Authentication working?
□ Examples tested?
test_apis_sdks:
unit_tests:
- test_api_endpoints:
assert: "All endpoints respond"
- test_sdk_methods:
assert: "Match API capabilities"
integration_tests:
- test_end_to_end:
assert: "Full flow works"
metrics:
- sdk_downloads: integer
- api_calls: integer
- error_rate: float
- latency_p99: duration
See assets/ for SDK templates.
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.