API Documenter
alirezarezvani/claude-code-tresor
Auto-generate API documentation from code and comments. An agent skill from alirezarezvani/claude-code-tresor.
REST API design and development expert specializing in endpoint design, HTTP semantics, versioning, error handling, pagination, and OpenAPI documentation.
$ npx skills add cin12211/orca-q --skill rest-api-expert -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install cin12211/orca-q rest-api-expert --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/cin12211/orca-q.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agent/skills/rest-api-expert .claude/skills/rest-api-expert && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "rest-api-expert" agent skill from https://github.com/cin12211/orca-q/tree/main/.agent/skills/rest-api-expert into .claude/skills/rest-api-expert/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rest-api-expert", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/cin12211/orca-q/tree/main/.agent/skills/rest-api-expertType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add cin12211/orca-q --skill rest-api-expert -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install cin12211/orca-q rest-api-expert --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cin12211/orca-q.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agent/skills/rest-api-expert .agents/skills/rest-api-expert && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "rest-api-expert" agent skill from https://github.com/cin12211/orca-q/tree/main/.agent/skills/rest-api-expert into .agents/skills/rest-api-expert/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rest-api-expert", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add cin12211/orca-q --skill rest-api-expert -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install cin12211/orca-q rest-api-expert --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cin12211/orca-q.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agent/skills/rest-api-expert .cursor/skills/rest-api-expert && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "rest-api-expert" agent skill from https://github.com/cin12211/orca-q/tree/main/.agent/skills/rest-api-expert into .cursor/skills/rest-api-expert/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rest-api-expert", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/cin12211/orca-q.git --path .agent/skills/rest-api-expert--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add cin12211/orca-q --skill rest-api-expert -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install cin12211/orca-q rest-api-expert --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cin12211/orca-q.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agent/skills/rest-api-expert .gemini/skills/rest-api-expert && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "rest-api-expert" agent skill from https://github.com/cin12211/orca-q/tree/main/.agent/skills/rest-api-expert into .gemini/skills/rest-api-expert/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rest-api-expert", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install cin12211/orca-q rest-api-expertInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add cin12211/orca-q --skill rest-api-expert -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/cin12211/orca-q.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agent/skills/rest-api-expert .github/skills/rest-api-expert && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "rest-api-expert" agent skill from https://github.com/cin12211/orca-q/tree/main/.agent/skills/rest-api-expert into .github/skills/rest-api-expert/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rest-api-expert", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add cin12211/orca-q --skill rest-api-expert -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install cin12211/orca-q rest-api-expert --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cin12211/orca-q.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agent/skills/rest-api-expert .opencode/skills/rest-api-expert && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "rest-api-expert" agent skill from https://github.com/cin12211/orca-q/tree/main/.agent/skills/rest-api-expert into .opencode/skills/rest-api-expert/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rest-api-expert", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
rest-api-expertREST API design and development expert specializing in endpoint design, HTTP semantics, versioning, error handling, pagination, and OpenAPI documentation.
REST API Expert is an agent skill from cin12211/orca-q. REST API design and development expert specializing in endpoint design, HTTP semantics, versioning, error handling, pagination, and OpenAPI documentation. Use PROACTIVELY for API architecture decisions, endpoint design issues, HTTP status code selection, or API documentation needs.
Its SKILL.md is about 3.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Backend & APIs, covering REST APIs, Technical documentation and OpenAPI specifications. It works with OpenAPI. The repository describes itself as: The open source | Next Generation database editor. The licence is MIT.
4 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 3142fe6. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are typescript and bash).
From the folder's file list and the shell code blocks in SKILL.md.
Links to these hosts (documentation or services it may open):
restfulapi.netics.uci.eduFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
REST API Expert loads about 3.2k tokens when it runs. Until then it costs about 75 tokens; SKILL.md has 434 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from cin12211/orca-q at commit 3142fe6, republished under its MIT licence (© cin12211). 434 words, ~3,195 tokens.
.claude/skills/rest-api-expert/SKILL.md (or your agent's skills folder).You are an expert in REST API design and development with deep knowledge of HTTP semantics, resource modeling, versioning strategies, error handling, and API documentation.
If the issue is specifically about:
# Check for API framework
grep -r "express\|fastify\|koa\|nestjs\|hono" package.json 2>/dev/null
# Check for OpenAPI/Swagger
ls -la swagger.* openapi.* 2>/dev/null
find . -name "*.yaml" -o -name "*.json" | xargs grep -l "openapi" 2>/dev/null | head -3
# Check existing API routes
find . -type f \( -name "*.ts" -o -name "*.js" \) -path "*/routes/*" -o -path "*/controllers/*" | head -10Common Issues:
Prioritized Fixes:
RESTful URL Design:
// ❌ BAD: Verb-based endpoints
GET /getUsers
POST /createUser
PUT /updateUser/123
DELETE /deleteUser/123
GET /getUserOrders/123
// ✅ GOOD: Resource-based endpoints
GET /users # List users
POST /users # Create user
GET /users/123 # Get user
PUT /users/123 # Update user (full)
PATCH /users/123 # Update user (partial)
DELETE /users/123 # Delete user
GET /users/123/orders # User's orders (nested resource)
// ✅ GOOD: Filtering, sorting, pagination
GET /users?status=active&sort=-createdAt&page=2&limit=20
// ✅ GOOD: Search as sub-resource
GET /users/search?q=john&fields=name,email
// ✅ GOOD: Actions as sub-resources (when needed)
POST /users/123/activate # Action on resource
POST /orders/456/cancel # State transitionResources:
Common Issues:
HTTP Methods Semantics:
// Method characteristics
// GET - Safe, Idempotent, Cacheable
// POST - Not Safe, Not Idempotent
// PUT - Not Safe, Idempotent
// PATCH - Not Safe, Not Idempotent
// DELETE - Not Safe, Idempotent
// Express example with proper methods
import { Router } from 'express';
const router = Router();
// GET - Retrieve resources (safe, idempotent)
router.get('/products', listProducts);
router.get('/products/:id', getProduct);
// POST - Create resources (not idempotent)
router.post('/products', createProduct);
// PUT - Replace entire resource (idempotent)
router.put('/products/:id', replaceProduct);
// PATCH - Partial update (not idempotent typically)
router.patch('/products/:id', updateProduct);
// DELETE - Remove resource (idempotent)
router.delete('/products/:id', deleteProduct);Status Code Guide:
// 2xx Success
200 OK // GET success, PUT/PATCH success with body
201 Created // POST success (include Location header)
204 No Content // DELETE success, PUT/PATCH success without body
// 3xx Redirection
301 Moved Permanently // Resource URL changed permanently
304 Not Modified // Cached response is still valid
// 4xx Client Errors
400 Bad Request // Invalid request body/params
401 Unauthorized // Missing or invalid authentication
403 Forbidden // Authenticated but not authorized
404 Not Found // Resource doesn't exist
405 Method Not Allowed // HTTP method not supported
409 Conflict // State conflict (e.g., duplicate)
422 Unprocessable Entity // Validation errors
429 Too Many Requests // Rate limit exceeded
// 5xx Server Errors
500 Internal Server Error // Unexpected server error
502 Bad Gateway // Upstream service error
503 Service Unavailable // Temporary overload/maintenanceCommon Issues:
Standard Error Response Format:
// Error response structure
interface ApiError {
status: number; // HTTP status code
code: string; // Application-specific error code
message: string; // Human-readable message
details?: ErrorDetail[]; // Field-level errors (for validation)
requestId?: string; // For debugging/support
timestamp?: string; // ISO 8601
}
interface ErrorDetail {
field: string;
message: string;
code: string;
}
// Example responses
// 400 Bad Request - Validation Error
{
"status": 400,
"code": "VALIDATION_ERROR",
"message": "Request validation failed",
"details": [
{ "field": "email", "message": "Invalid email format", "code": "INVALID_EMAIL" },
{ "field": "age", "message": "Must be at least 18", "code": "MIN_VALUE" }
],
"requestId": "req_abc123",
"timestamp": "2024-01-15T10:30:00Z"
}
// 404 Not Found
{
"status": 404,
"code": "RESOURCE_NOT_FOUND",
"message": "User with ID '123' not found",
"requestId": "req_def456",
"timestamp": "2024-01-15T10:30:00Z"
}
// 500 Internal Server Error
{
"status": 500,
"code": "INTERNAL_ERROR",
"message": "An unexpected error occurred. Please try again later.",
"requestId": "req_ghi789",
"timestamp": "2024-01-15T10:30:00Z"
}Error Handling Middleware:
// Express error handler
import { Request, Response, NextFunction } from 'express';
class AppError extends Error {
constructor(
public status: number,
public code: string,
message: string,
public details?: ErrorDetail[]
) {
super(message);
}
}
function errorHandler(
err: Error,
req: Request,
res: Response,
next: NextFunction
) {
const requestId = req.headers['x-request-id'] || generateRequestId();
if (err instanceof AppError) {
return res.status(err.status).json({
status: err.status,
code: err.code,
message: err.message,
details: err.details,
requestId,
timestamp: new Date().toISOString(),
});
}
// Log unexpected errors
console.error('Unexpected error:', err);
// Don't expose internal errors to clients
return res.status(500).json({
status: 500,
code: 'INTERNAL_ERROR',
message: 'An unexpected error occurred',
requestId,
timestamp: new Date().toISOString(),
});
}Common Issues:
Pagination Strategies:
// 1. Offset-based pagination (simple, but slow for large offsets)
GET /products?page=2&limit=20
{
"data": [...],
"pagination": {
"page": 2,
"limit": 20,
"total": 150,
"totalPages": 8,
"hasNext": true,
"hasPrev": true
}
}
// 2. Cursor-based pagination (efficient for large datasets)
GET /products?cursor=eyJpZCI6MTAwfQ&limit=20
{
"data": [...],
"pagination": {
"limit": 20,
"nextCursor": "eyJpZCI6MTIwfQ",
"prevCursor": "eyJpZCI6ODB9",
"hasNext": true,
"hasPrev": true
}
}
// Implementation example
async function paginateWithCursor(
cursor: string | null,
limit: number = 20
) {
const decodedCursor = cursor
? JSON.parse(Buffer.from(cursor, 'base64').toString())
: null;
const items = await prisma.product.findMany({
take: limit + 1, // Fetch one extra to check hasNext
cursor: decodedCursor ? { id: decodedCursor.id } : undefined,
skip: decodedCursor ? 1 : 0,
orderBy: { id: 'asc' },
});
const hasNext = items.length > limit;
const data = hasNext ? items.slice(0, -1) : items;
return {
data,
pagination: {
limit,
nextCursor: hasNext
? Buffer.from(JSON.stringify({ id: data[data.length - 1].id })).toString('base64')
: null,
hasNext,
},
};
}Common Issues:
Versioning Strategies:
// 1. URL Path Versioning (recommended)
GET /api/v1/users
GET /api/v2/users
// Implementation
import { Router } from 'express';
const v1Router = Router();
const v2Router = Router();
// V1 routes
v1Router.get('/users', getUsersV1);
// V2 routes with breaking changes
v2Router.get('/users', getUsersV2);
app.use('/api/v1', v1Router);
app.use('/api/v2', v2Router);
// 2. Header Versioning
GET /api/users
Accept: application/vnd.myapi.v2+json
// 3. Query Parameter (not recommended for APIs)
GET /api/users?version=2Deprecation Headers:
// Communicate deprecation
res.setHeader('Deprecation', 'true');
res.setHeader('Sunset', 'Sat, 01 Jun 2025 00:00:00 GMT');
res.setHeader('Link', '</api/v2/users>; rel="successor-version"');Common Issues:
Request/Response Best Practices:
// Consistent naming convention (pick one, stick to it)
// JavaScript/TypeScript typically uses camelCase
// Request validation with Zod
import { z } from 'zod';
const CreateUserSchema = z.object({
email: z.string().email(),
name: z.string().min(2).max(100),
age: z.number().int().min(18).optional(),
role: z.enum(['user', 'admin']).default('user'),
});
// Validate in middleware
function validate(schema: z.ZodSchema) {
return (req: Request, res: Response, next: NextFunction) => {
try {
req.body = schema.parse(req.body);
next();
} catch (error) {
if (error instanceof z.ZodError) {
return res.status(400).json({
status: 400,
code: 'VALIDATION_ERROR',
message: 'Request validation failed',
details: error.errors.map(e => ({
field: e.path.join('.'),
message: e.message,
code: e.code,
})),
});
}
next(error);
}
};
}
// Response envelope for consistency
interface ApiResponse<T> {
data: T;
meta?: {
pagination?: PaginationInfo;
[key: string]: any;
};
}
// Partial responses (field selection)
GET /users/123?fields=id,name,email/createUser, /updateProduct → Use nouns with HTTP methods© cin12211, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in .agent/skills/rest-api-expert of cin12211/orca-q.
Open the folder on GitHubat commit 3142fe6
REST API Expert next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| REST API Expert this skillcin12211/orca-q | 224 | — | ~3.2k | Automated safety check: Pass | MIT | |
| API Documenteralirezarezvani/claude-code-tresor | 777 | — | ~1.5k | Automated safety check: Pass | MIT | |
| OpenAPI Spec Generationwshobson/agents | 40k | 10 repos | ~511 | Automated safety check: Pass | MIT | |
| Document API Endpointgetsentry/skills | 1k | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Spring Boot Openapi Documentationgiuseppe-trisciuoglio/developer-kit | 355 | 1 repos | ~2.6k | Automated safety check: Notes | MIT | |
| REST API Designcuriositech/some_claude_skills | 243 | 1 repos | ~3.1k | Automated safety check: Pass | MIT |
alirezarezvani/claude-code-tresor
Auto-generate API documentation from code and comments. An agent skill from alirezarezvani/claude-code-tresor.
wshobson/agents
Create, validate and maintain OpenAPI 3.1 specs for REST APIs, whether designed first or generated from existing code, and use them for docs and client SDKs.
getsentry/skills
Document and type a Sentry API endpoint. An agent skill from getsentry/skills.
giuseppe-trisciuoglio/developer-kit
Provides patterns to generate comprehensive REST API documentation using SpringDoc OpenAPI 3.0 and Swagger UI in Spring Boot 3.x applications.
curiositech/some_claude_skills
Design REST API endpoints with Zod validation and OpenAPI documentation.
secondsky/claude-skills
Creates professional API documentation using OpenAPI specifications with endpoints, authentication, and interactive examples.
cin12211/orca-q
TypeScript and JavaScript expert with deep knowledge of type-level programming, performance optimization, monorepo management, migration strategies, and modern tooling.
cin12211/orca-q
Database performance optimization, schema design, query analysis, and connection management across PostgreSQL, MySQL, MongoDB, and SQLite with ORM integration.
cin12211/orca-q
Playwright E2E testing expert for browser automation, cross-browser testing, visual regression, network interception, and CI integration.
cin12211/orca-q
Specialized research expert for parallel information gathering.
cin12211/orca-q
OrcaQ-specific testing guide. An agent skill from cin12211/orca-q.
cin12211/orca-q
PostgreSQL query optimization, JSONB operations, advanced indexing strategies, partitioning, connection management, and database administration.
Works with
Categories
REST API design and development expert specializing in endpoint design, HTTP semantics, versioning, error handling, pagination, and OpenAPI documentation. REST API Expert is an agent skill from cin12211/orca-q. REST API design and development expert specializing in endpoint design, HTTP semantics, versioning, error handling, pagination, and OpenAPI documentation.
REST API Expert fits situations like: tasks that involve REST APIs; tasks that involve Technical documentation; tasks that involve OpenAPI specifications.
Run `npx skills add cin12211/orca-q --skill rest-api-expert -a claude-code`. Or copy the skill folder (.agent/skills/rest-api-expert in cin12211/orca-q) into .claude/skills/rest-api-expert in your project. Claude Code loads it when a task matches its description.
Run `npx skills add cin12211/orca-q --skill rest-api-expert -a codex`. Or copy the skill folder (.agent/skills/rest-api-expert in cin12211/orca-q) into .agents/skills/rest-api-expert in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add cin12211/orca-q --skill rest-api-expert -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/rest-api-expert, .gemini/skills/rest-api-expert, .github/skills/rest-api-expert and .opencode/skills/rest-api-expert in your project.
SKILL.md names no scripts, command-line tools or credentials: REST API Expert is instructions for the agent only.
SKILL.md names 2 domains. As links in the text: restfulapi.net and ics.uci.edu. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
REST API Expert is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 3.2k tokens (SKILL.md is roughly 13k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with REST API Expert: API Documenter (alirezarezvani/claude-code-tresor, 777 stars), OpenAPI Spec Generation (wshobson/agents, 40k stars), Document API Endpoint (getsentry/skills, 1k stars) and Spring Boot Openapi Documentation (giuseppe-trisciuoglio/developer-kit, 355 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
cin12211 (a GitHub user) maintains it in cin12211/orca-q, which has 224 GitHub stars. The repository holds 16 skills in this directory. The repository was last updated on September 21, 2026.
Source: cin12211/orca-q on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.