api-documentation

Generate OpenAPI and Swagger documentation for REST and GraphQL APIs.

1|Updated Aug 10, 2025
One-click install
npx skills add https://github.com/michsindlinger/agent-os-extended --skill api-documentation-michsindlinger
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: api-documentation
Source: https://github.com/michsindlinger/agent-os-extended/tree/main/agent-os/templates/skills/dev-team/documenter/api-documentation
Command: npx skills add https://github.com/michsindlinger/agent-os-extended --skill api-documentation-michsindlinger

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of detailed API documentation, ensuring clarity and consistency for developers and stakeholders.

Core Features & Use Cases

  • OpenAPI/Swagger Generation: Creates machine-readable specifications for REST APIs.
  • Schema Definition: Extracts and documents data models.
  • Example Generation: Provides clear request and response examples.
  • Use Case: After developing a new set of API endpoints for user management, use this Skill to generate an OpenAPI 3.0 specification that can be used to power interactive documentation (Swagger UI) and client SDK generation.

Quick Start

Generate OpenAPI documentation for the current API project.

Frequently Asked Questions about api-documentation

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

FAQPage Schema
How do I generate OpenAPI documentation from an existing REST API?

Generate OpenAPI documentation by extracting endpoint definitions and data models to produce OpenAPI 3.0 specifications. This Skill automates schema generation, creates request and response examples, and outputs files compatible with Swagger UI and Redoc.

Can I generate Swagger specs for a Node.js Express or Ruby on Rails project?

Yes, you can generate Swagger specs for Node.js/Express and Ruby on Rails projects. The Skill integrates with tech stacks using tools like swagger-jsdoc and rswag to create machine-readable specifications from your existing API endpoints.

What's the best way to document GraphQL API schemas and endpoints?

Document GraphQL APIs by extracting schema definitions and generating endpoint documentation using graphql-docs. This approach creates detailed, interactive documentation interfaces that clarify queries, mutations, and data models for developers and stakeholders.

Does this API documentation approach support interactive interfaces like Swagger UI?

Yes, API documentation generated through this method supports interactive interfaces like Swagger UI and Redoc. Creating OpenAPI 3.0 specifications allows you to directly power interactive documentation and automated client SDK generation.

How do I create request and response examples for my API documentation?

Create request and response examples through automated example generation included in the documentation workflow. The Skill extracts data models and generates clear, representative examples for your REST and GraphQL API endpoints automatically.

Why use rswag to generate Swagger documentation for Ruby on Rails APIs?

Use rswag to generate Swagger documentation because it integrates directly with Ruby on Rails to produce OpenAPI-compatible specs. This ensures consistency, enables interactive Swagger UI integration, and automates schema definition extraction from your routes.