Generate external API documentation in HTML format for Squint APIs. Use when asked to document an API endpoint, create API docs for external consumers, or generate HTML documentation for endpoints. Output is Google Docs compatible.
Installation
Details
Usage
After installing, this skill will be available to your AI coding assistant.
Verify installation:
npx agent-skills-cli listSkill Instructions
name: api-docs description: Generate external API documentation in HTML format for Squint APIs. Use when asked to document an API endpoint, create API docs for external consumers, or generate HTML documentation for endpoints. Output is Google Docs compatible.
API Documentation Generator
Generate HTML API docs for Squint endpoints.
Investigation Process
Before writing docs, gather information from the codebase:
- Find the router - Search
api/src/infrastructure/routes/for the relevant router file - Identify the handler - Find the handler function (e.g.,
GetProceduresHandler) - Read the service - Located in
api/src/infrastructure/services/- understand request validation, query params, and response assembly - Find response types - Check imports from
@squintinc/datamodels-ts-cloud/v1or look for Zod schemas - Check repository - In
api/src/infrastructure/repositories/for SQL queries showing exact response shape - Identify sub-objects - Note nested objects that need separate field tables
Documentation Structure
Each endpoint doc includes:
- Title:
{HTTP_METHOD} {Endpoint Name} Endpoint - Endpoint path: Full path pattern
- Description: 1-2 sentences explaining what the endpoint does
- Authentication: Bearer token requirement and required permission
- Request: Headers table, Path/Query Parameters tables, Request Body (if applicable)
- Response: Example JSON, Response Fields table, Sub-object tables
- Error Responses table
Field Type Conventions
| Code Type | Doc Type |
|---|---|
string (UUID format) | UUID |
string | string |
number, int | integer |
number (decimal) | float |
boolean | boolean |
Date, DateSchema | ISO 8601 |
string[] | string[] |
SomeType[] | array |
| Nested object | object (reference sub-object table) |
Authentication Patterns
Integrations API (/v1/integrations/...)
For API key authentication, document as:
- "Requires a valid API key with
{permission}permission" - Format:
Authorization: Bearer <prefix>:<secret>
Authenticated API (/v1/workspaces/...)
For Firebase JWT authentication, document as:
- "Requires a valid workspace scoped Bearer token with {permission} permission"
- Format:
Authorization: Bearer <token>
JSON Example Guidelines
- Use realistic fake UUIDs (e.g.,
f1e2d3c4-b5a6-7890-cdef-1234567890ab) - Use ISO 8601 timestamps (e.g.,
2025-01-06T10:00:00.000Z) - Show
nullfor nullable fields commonly null - Include 1-2 items for arrays
- Show complete structure for nested objects
Output Location
Write HTML files to docs/api-docs/api/v1/:
docs/api-docs/api/v1/
├── integrations/workspaces/ # /v1/integrations/workspaces/{workspaceId}/...
└── workspaces/ # /v1/workspaces/{workspaceId}/...
Naming: {resource}.html or {resource}-{action}.html (e.g., tasks-create.html)
HTML Templates
See references/html-templates.md for:
- Base HTML document structure
- Table formats (Headers, Parameters, Response Fields, Errors)
- Sub-object documentation patterns
- Authentication section formats
Viewing Documentation
To preview HTML docs locally in VS Code/Cursor:
- Install the Live Preview extension
- Open any
.htmlfile - Click "Show Preview" or right-click → "Live Preview: Show Preview"
More by kvnxiao
View allCreate isolated git worktrees in ~/.claude-worktrees/. Use when user says "create an isolated copy", "worktree", "create worktree", "isolated workspace", or needs to work on a branch without affecting the main working directory.
Review and improve repository documentation including both human-readable docs (`docs/`), `README.md`, and AI agent memory context files (`CLAUDE.md`, `CODEX.md`, `AGENTS.md`, `.cursorrules`, etc.) for clarity, minimal duplication, and modularity. Use when asked to review, audit, refactor, or improve documentation structure, consolidate rules, reduce redundancy, establish shared standards, or modularize monolithic instruction files.
