Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
aj-geddes avatar

Api Reference Documentation

  • 443 installs
  • 305 repo stars
  • Updated March 4, 2026
  • aj-geddes/useful-ai-prompts

api-reference-documentation is a useful-ai-prompts skill that generates complete API reference pages with endpoint tables, auth examples, request/response schemas, and error code matrices for developers publishing develo

About

api-reference-documentation is a skill from aj-geddes/useful-ai-prompts that drafts full API reference pages for developer portals. It structures endpoint tables, authentication examples, request and response schemas, and error code matrices so public API docs read consistently for integrators. Developers reach for api-reference-documentation when an API surface exists or is stabilizing and portal pages must be generated or refreshed faster than hand-writing every endpoint section, especially before external developers need self-serve integration guidance.

  • Structures endpoint reference sections
  • Documents auth, headers, and errors
  • Includes request and response examples
  • Covers rate limits and versioning notes

Api Reference Documentation by the numbers

  • 443 all-time installs (skills.sh)
  • Ranked #398 of 1,879 Documentation skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/aj-geddes/useful-ai-prompts --skill api-reference-documentation

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs443
repo stars305
Last updatedMarch 4, 2026
Repositoryaj-geddes/useful-ai-prompts

How do you write API reference docs for a developer portal?

Generate complete API reference pages with endpoint tables, auth examples, request/response schemas, and error code matrices for developer portals.

Who is it for?

Backend developers or technical writers documenting REST or HTTP APIs who need complete portal-ready reference pages from existing endpoint knowledge.

Skip if: Developers who only need OpenAPI YAML without narrative portal pages, because api-reference-documentation targets human-readable reference documentation.

When should I use this skill?

The user needs API reference pages with endpoints, auth examples, schemas, or error matrices for a developer portal.

What you get

API reference pages with endpoint tables, authentication examples, request/response schemas, and error code matrices.

  • API reference pages
  • Endpoint tables
  • Error code matrices

Files

SKILL.mdMarkdownGitHub ↗

API Reference Documentation

Table of Contents

Overview

Generate professional API documentation that developers can use to integrate with your API, including endpoint specifications, authentication, request/response examples, and interactive documentation.

When to Use

  • Documenting REST APIs
  • Creating OpenAPI/Swagger specifications
  • GraphQL API documentation
  • SDK and client library docs
  • API authentication guides
  • Rate limiting documentation
  • Webhook documentation
  • API versioning guides

Quick Start

Minimal working example:

openapi: 3.0.3
info:
  title: E-Commerce API
  description: |
    Complete API for managing e-commerce operations including products,
    orders, customers, and payments.

    ## Authentication
    All endpoints require Bearer token authentication. Include your API key
    in the Authorization header: `Authorization: Bearer YOUR_API_KEY`

    ## Rate Limiting
    - 1000 requests per hour for authenticated users
    - 100 requests per hour for unauthenticated requests

    ## Pagination
    List endpoints return paginated results with `page` and `limit` parameters.
  version: 2.0.0
  contact:
    name: API Support
    email: api@example.com
    url: https://example.com/support
  license:
    name: MIT
    url: https://opensource.org/licenses/MIT
// ... (see reference guides for full implementation)

Reference Guides

Detailed implementations in the references/ directory:

GuideContents
OpenAPI Specification Exampleopenapi: 3.0.3
List ProductsList Products

Best Practices

✅ DO

  • Use OpenAPI 3.0+ specification
  • Include request/response examples for every endpoint
  • Document all query parameters and headers
  • Provide authentication examples
  • Include error response formats
  • Document rate limits and pagination
  • Use consistent naming conventions
  • Include SDK examples in multiple languages
  • Document webhook payloads
  • Provide interactive API explorer (Swagger UI)
  • Version your API documentation
  • Include migration guides for breaking changes

❌ DON'T

  • Skip error response documentation
  • Forget to document authentication
  • Use inconsistent terminology
  • Leave endpoints undocumented
  • Ignore deprecation notices
  • Skip versioning information

Related skills

How it compares

Pick api-reference-documentation over generic doc templates when portal pages need endpoint tables, auth examples, schemas, and error matrices in one pass.

FAQ

What sections does api-reference-documentation generate?

api-reference-documentation generates endpoint tables, authentication examples, request and response schemas, and error code matrices. Together those sections form complete API reference pages suitable for a developer portal.

Who should use api-reference-documentation?

api-reference-documentation suits developers or technical writers documenting HTTP APIs for external integrators. Use it when portal pages must be drafted or refreshed faster than manual copy for every endpoint.

Documentationdocsbackend

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.