technical-writer-api-docs

Generate API reference pages from OpenAPI, GraphQL SDL, or code contracts.

6|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/lookatitude/guild --skill technical-writer-api-docs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: technical-writer-api-docs
Source: https://github.com/lookatitude/guild/tree/main/skills/specialists/technical-writer-api-docs
Command: npx skills add https://github.com/lookatitude/guild --skill technical-writer-api-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Documents an existing API contract into precise reference pages per endpoint, mirroring the source specification and preventing drift.

Core Features & Use Cases

  • Mirrors the contract exactly (OpenAPI/SDL/code) for every endpoint.
  • Includes authentication, pagination, error tables, and versioning notes.
  • Use Case: deliver developer-ready reference docs that map 1:1 to the contract, enabling curl/SDK examples without guessing.

Quick Start

Provide the API contract (OpenAPI/SDL) and let this skill generate reference pages for the requested endpoints.

Frequently Asked Questions about technical-writer-api-docs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate API reference docs from an OpenAPI specification?

API reference docs are generated by processing an OpenAPI or GraphQL SDL contract to produce exact endpoint pages mapping 1:1 to the source. This ensures fidelity and prevents drift by including method, path, parameters, and schemas.

What is the best way to prevent API documentation drift from code-level contracts?

Preventing API documentation drift is achieved by mirroring the source specification exactly for every endpoint. This generates precise reference pages that map 1:1 to the contract, ensuring strict fidelity and preventing inconsistencies.

Can I document GraphQL SDL endpoints using automated reference generation?

Automated reference generation supports GraphQL SDL endpoints by applying the process to the SDL contract. It produces a reusable reference structure with request/response schemas and a single runnable example per endpoint.

Does API reference documentation include authentication and pagination details?

API reference documentation includes authentication and pagination details alongside error tables and versioning notes. These elements ensure developer-ready reference pages that enable curl/SDK examples without guessing.

How do I create developer-ready API docs with runnable curl examples?

Creating developer-ready API docs with runnable curl examples involves mapping the API contract exactly into reference pages. This yields a single runnable example per endpoint, allowing developers to execute requests without guessing parameters.