API service
Provides patterns for building clean, documented HTTP API surfaces and request/response models.
Install
mkdir -p .claude/skills/api-service && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/10306" && unzip -o skill.zip -d .claude/skills/api-service && rm skill.zipInstalls to .claude/skills/api-service
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Use this skill when: - adding HTTP endpoints; - defining request and response models; - wiring document generation into an API surface; - shaping controller, route, or handler behavior.Key capabilities
- →Add HTTP endpoints
- →Define request and response models
- →Wire document generation into API surface
- →Shape controller and route behavior
- →Validate inputs at the boundary
How it works
The skill promotes a thin API layer by delegating business logic to dedicated service classes and ensuring input validation occurs at the boundary.
Inputs & outputs
When to use API service
- →Add a new HTTP endpoint
- →Define request and response DTOs
- →Refactor controller logic
- →Integrate document generation into an API
About this skill
API service
Use this skill when:
- adding HTTP endpoints;
- defining request and response models;
- wiring document generation into an API surface;
- shaping controller, route, or handler behavior.
Goals
- Keep the API surface small and explicit.
- Validate inputs close to the boundary.
- Keep endpoint logic thin by delegating work to focused services.
Recommended approach
- Define request and response contracts clearly.
- Keep endpoint code responsible for validation, orchestration, and status mapping.
- Move document-generation logic into dedicated service classes or functions.
- Return errors consistently and avoid leaking internal details.
- Document any new endpoint behavior in the README or docs when applicable.
Output expectations
- Thin API layer.
- Clear request/response models.
- Separation between transport and generation logic.
When not to use it
- →When business logic should remain inside the API controller
Limitations
- →Requires delegation of work to focused services
- →Must avoid leaking internal details in error responses
How it compares
It enforces a separation of concerns between transport logic and business logic, preventing the API surface from becoming bloated.
Compared to similar skills
API service side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| API service (this skill) | 0 | 2mo | No flags | Beginner |
| generating-grpc-services | 1 | 26d | Review | Advanced |
| senior-backend | 0 | 4mo | Review | Advanced |
| backend-development | 0 | 5mo | No flags | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
generating-grpc-services
jeremylongshore
Generate gRPC service definitions, stubs, and implementations from Protocol Buffers. Use when creating high-performance gRPC services. Trigger with phrases like "generate gRPC service", "create gRPC API", or "build gRPC server".
senior-backend
Cor-Incorporated
Guides backend system development with Node.js, Express, Go, Python, PostgreSQL, GraphQL, and REST APIs. Use when the user says: 'design an API', 'optimize database queries', 'implement authentication', 'set up backend', 'create API endpoint', 'database migration', 'fix N+1 query', 'add rate limitin
backend-development
hoadh
Build backends with Node.js, Python, Go (NestJS, FastAPI, Django). Use for REST/GraphQL/gRPC APIs, auth (OAuth, JWT), databases, microservices, security (OWASP), Docker/K8s.
api-dev
ComeOnOliver
Modern API development patterns for building high-performance, scalable web services. Expert in async/await patterns, REST/GraphQL APIs, middleware, error handling, rate limiting, OpenAPI documentation, testing, and production optimizations. Framework-agnostic patterns that work with Python, Node.js
architecture-patterns
wshobson
Implement proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design. Use when architecting complex backend systems or refactoring existing applications for better maintainability.
backend-expert
FlavioProgramador
Advanced backend engineering guidelines focusing on clean architecture, API standards, performance, asynchronous jobs, and clean code principles.