api-doc-writer

Generate structured REST API documentation in Markdown from interface requirements.

195|12|Updated Jul 19, 2026
One-click install
npx skills add https://github.com/ZJU-REAL/HugAgentOS --skill api-doc-writer-zju-real
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: api-doc-writer
Source: https://github.com/ZJU-REAL/HugAgentOS/tree/main/src/backend/skill_bundles/marketplace/api-doc-writer
Command: npx skills add https://github.com/ZJU-REAL/HugAgentOS --skill api-doc-writer-zju-real

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill reduces the effort and inconsistency involved in documenting REST APIs by providing a structured format for endpoints, parameters, requests, responses, errors, authentication, and version changes.

Core Features & Use Cases

  • REST API Documentation: Create organized documentation for resource-based endpoints, including methods, URLs, parameters, request examples, and response examples.
  • Interface Standards: Define RESTful naming conventions, HTTP method usage, status codes, authentication practices, and security recommendations.
  • Use Case: Use it to turn a user, order, or payment API design into a consistent reference document that developers can implement and maintain.

Quick Start

Ask the API documentation skill to generate a complete REST API specification for your user and order endpoints, including authentication, parameters, examples, error responses, and a change log.

Frequently Asked Questions about api-doc-writer

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

FAQPage Schema
How do I generate REST API documentation from interface requirements?

To generate REST API documentation, provide your interface requirements and endpoint designs to produce structured Markdown references covering methods, parameters, and examples. This process ensures consistent documentation for resource-based endpoints without manual formatting effort.

What is the best way to document RESTful endpoint standards and HTTP methods?

Documenting RESTful endpoint standards involves defining naming conventions, HTTP method usage, and status codes within a structured specification. This establishes consistent interface guidelines for developers implementing resource-based CRUD operations and security practices.

Can I create Markdown reference documents for CRUD operations and security recommendations?

Yes, you can create Markdown reference documents that cover common CRUD operations, authentication guidance, and security recommendations. This output provides developers with clear, usable interface specifications for maintaining API endpoints.

How do I include error definitions and request response examples in my API specification?

Including error definitions and request response examples requires mapping your interface designs to structured documentation formats. This yields a complete API specification with parameter details, response payloads, and error handling guidance for developers.

Does API documentation generation support change log maintenance and version changes?

API documentation generation supports change log maintenance by structuring version changes alongside interface specifications. This ensures your endpoint reference documents track modifications consistently across API iterations.

What should I provide to turn an API design into a consistent reference document?

To turn an API design into a consistent reference document, provide your interface requirements and endpoint designs. The skill outputs structured Markdown covering endpoints, parameters, examples, errors, and authentication guidance for your user or order APIs.