documentation

To generate a runbook for standard operational procedures, this Skill automates creating Markdown documents detailing prerequisites, step-by-step instructions, rollback steps, and escalation paths for common operational tasks.

The best way to write API documentation with endpoint references is using this Skill to generate detailed Markdown references covering examples, authentication notes, error codes, rate limits, pagination, and SDK samples.

To create an onboarding guide for a new software project, this Skill automates generating Markdown guides detailing environment setup, key system connections, common task walkthroughs, and contact information for new team members.

Yes, you can include architecture notes and design trade-offs in technical documentation. This Skill generates architecture documents capturing context, high-level design, key decisions, data flow, and integration points.

Yes, the generated technical documentation supports frontmatter-driven metadata. The Skill produces Markdown files with structured document outlines and frontmatter metadata, supporting optional scripts, references, and assets.

A README for quick start and configuration guidance should include usage instructions and contribution guidelines. This Skill automates generating these README sections alongside API references, runbooks, and onboarding guides.