api-implementer
Implements API endpoints, routes, controllers, and request/response handling. Use when implementing REST APIs, GraphQL APIs, or other API endpoints. Handles routing, validation, error handling, and response formatting.
Best use case
api-implementer is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Implements API endpoints, routes, controllers, and request/response handling. Use when implementing REST APIs, GraphQL APIs, or other API endpoints. Handles routing, validation, error handling, and response formatting.
Teams using api-implementer should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/api-implementer/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How api-implementer Compares
| Feature / Agent | api-implementer | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Implements API endpoints, routes, controllers, and request/response handling. Use when implementing REST APIs, GraphQL APIs, or other API endpoints. Handles routing, validation, error handling, and response formatting.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# API Implementer Skill
## Instructions
1. Analyze API requirements from task
2. Review API specifications (endpoints, request/response formats)
3. Implement API endpoints with proper routing
4. Add request validation
5. Implement error handling
6. Format responses correctly
7. Return implementation with:
- Route definitions
- Controller/handler functions
- Validation logic
- Error handling
- Response formatting
## Examples
**Input:** "Implement POST /api/tasks endpoint"
**Output:**
```javascript
// routes/tasks.js
router.post('/api/tasks', authenticate, validateTaskInput, async (req, res) => {
try {
const task = await createTask({
title: req.body.title,
description: req.body.description,
userId: req.user.id
});
res.status(201).json(task);
} catch (error) {
res.status(400).json({ error: error.message });
}
});
// middleware/validation.js
function validateTaskInput(req, res, next) {
if (!req.body.title || req.body.title.trim().length === 0) {
return res.status(400).json({ error: 'Title is required' });
}
if (req.body.title.length > 255) {
return res.status(400).json({ error: 'Title must be 255 characters or less' });
}
next();
}
```
## API Implementation Areas
- **Route Definition**: HTTP method, path, middleware
- **Request Handling**: Parse request body, query params, headers
- **Validation**: Input validation, data sanitization
- **Business Logic**: Core functionality implementation
- **Error Handling**: Proper error responses, status codes
- **Response Formatting**: Consistent response structure
- **Authentication**: Auth middleware, token validation
- **Authorization**: Permission checks, role-based access
## Best Practices
- **RESTful Design**: Follow REST conventions
- **Consistent Responses**: Standard response format
- **Proper Status Codes**: Use appropriate HTTP status codes
- **Error Handling**: Comprehensive error handling
- **Validation**: Validate all inputs
- **Documentation**: Document endpoints and parametersRelated Skills
ui-implementer
Implements UI components from scratch based on design references (Figma, screenshots, mockups) with intelligent validation and adaptive agent switching. Use when user provides a design and wants pixel-perfect UI implementation with design fidelity validation. Triggers automatically when user mentions Figma links, design screenshots, or wants to implement UI from designs.
bgo
Automates the complete Blender build-go workflow, from building and packaging your extension/add-on to removing old versions, installing, enabling, and launching Blender for quick testing and iteration.
1k-error-handling
Error handling patterns and best practices for OneKey. Use when implementing try/catch blocks, handling async errors, showing error messages, or managing error states in UI. Triggers on error, try, catch, exception, throw, fail, failure, error handling, error boundary, useAsyncCall, toast, fallback, error state.
1k-dev-commands
Development commands for OneKey monorepo. Use when running dev servers, building apps, linting, testing, or troubleshooting build issues. Triggers on yarn, dev, build, lint, test, desktop, mobile, web, extension, ios, android, compile, bundle.
1k-date-formatting
Date and time formatting for OneKey applications. Use when displaying dates, timestamps, or formatting time in UI components. Always use OneKey utilities instead of native JS date methods. Triggers on date, time, timestamp, formatDate, formatTime, toLocaleDateString, toLocaleString, dateUtils, locale, format, display date, show time, datetime, calendar.
1k-cross-platform
Cross-platform development patterns for OneKey. Use when writing platform-specific code, handling platform differences, or working with native/web/desktop/extension platforms. Triggers on platform, native, web, desktop, extension, iOS, Android, Electron, platformEnv, .native.ts, .web.ts, .desktop.ts, .ext.ts, cross-platform, multi-platform.
1k-coding-patterns
Coding patterns and best practices for OneKey development. Use when writing React components, handling promises, error handling, or following code conventions. Triggers on react, component, hooks, promise, async, await, error, pattern, convention, typescript.
1k-architecture
OneKey monorepo architecture and code organization. Use when understanding project structure, package relationships, import rules, or component organization. Triggers on architecture, structure, packages, imports, hierarchy, dependencies, monorepo, organization.
1k-app-upgrade-test
Create test versions to verify app auto-update functionality. Use when testing update flows, version migration, or validating app upgrade mechanisms. Automates version number and build number configuration for testing the auto-update system. Triggers on auto update, app upgrade, update testing, upgrade flow, version migration, test build, 9XXX version.
1k-adding-socket-events
Adds new WebSocket event subscriptions to OneKey. Use when implementing new socket events, handling server push messages, or adding real-time data subscriptions. Socket, WebSocket, event, subscription, push, real-time.
1d-cutting-stock
When the user wants to cut 1D materials optimally, minimize waste in linear cutting, or solve one-dimensional cutting stock problems. Also use when the user mentions "1D cutting," "linear cutting optimization," "rod cutting," "pipe cutting," "beam cutting," "trim loss," "cutting stock problem," "pattern generation," or "column generation for cutting." For 2D problems, see 2d-cutting-stock. For general trim loss, see trim-loss-minimization.
1c-bsl-code-generation
Skill for generating 1C:Enterprise (BSL) code with mandatory validation through MCP tools to prevent hallucinations. Use when generating, editing, or validating 1C BSL code, working with 1C metadata, or answering questions about 1C platform API.