api-documentation

Generate OpenAPI/Swagger-compatible API documentation from definitions, schemas, and annotations.

8|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/JEO-tech-ai/oh-my-unity3d --skill api-documentation-jeo-tech-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: api-documentation
Source: https://github.com/JEO-tech-ai/oh-my-unity3d/tree/main/.unity-skills/api-documentation
Command: npx skills add https://github.com/JEO-tech-ai/oh-my-unity3d --skill api-documentation-jeo-tech-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

API documentation is often tedious and error-prone when hand-written; this Skill converts API definitions, schemas, and code annotations into comprehensive, developer-friendly references and interactive docs.

Core Features & Use Cases

  • OpenAPI/Swagger spec generation from REST and GraphQL APIs
  • Interactive documentation setup (Swagger UI / OpenAPI UI)
  • SDK/reference guide generation and example-driven docs for developer portals
  • Versioned references and change-tracking to align docs with releases

Quick Start

Use the API documentation skill to generate OpenAPI/Swagger-ready documentation from your API definitions and code comments.

Frequently Asked Questions about api-documentation

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

FAQPage Schema
Why does hand-written API documentation become outdated or error-prone?

Automated API documentation generation converts API definitions, schemas, and code annotations into comprehensive developer-ready references. It eliminates error-prone manual writing by producing OpenAPI specs, interactive docs, and reference guides.

Does this API documentation generation work with CI/CD pipelines and versioning?

Yes, interactive documentation generation supports both REST and GraphQL projects. It produces Swagger UI and OpenAPI UI outputs from your API definitions, providing interactive exploration for developers.

What's the best way to create SDK reference guides and examples for developer portals?

Set up versioned API references by integrating documentation generation into CI/CD pipelines. This aligns versioned references and change-tracking outputs with API releases, keeping developer portals updated automatically.

Do I need code annotations to generate Swagger UI documentation?

Create SDK reference guides and example-driven docs by processing API definitions and schemas. This produces comprehensive reference materials and examples specifically formatted for developer portal integration.