create-documentation

Generate structured Markdown documentation with YAML frontmatter and audience sections.

Updated Mar 12, 2026

Search Tags:#documentation #markdown #frontmatter #mdx #documentation-generation #audience-analysis

Ready to run

npx skills add https://github.com/vddgmbh/documenso --skill create-documentation-vddgmbh

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-documentation
Source: https://github.com/vddgmbh/documenso/tree/main/.agents/skills/create-documentation
Command: npx skills add https://github.com/vddgmbh/documenso --skill create-documentation-vddgmbh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of clear Markdown documentation for a module or feature, reducing manual drafting time and ensuring consistent structure.

Core Features & Use Cases

Auto-creates feature docs from source context, including frontmatter, sections, and navigation references.
Guides writers through a standardized structure for different audiences (Users, Developers, Self-Hosters).
Supports updating existing documentation by aligning with code changes and existing meta/navigation.

Quick Start

Write a complete Markdown page for a given feature by summarizing its purpose, usage, and navigation metadata.

Frequently Asked Questions about create-documentation

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

FAQPage Schema

How do I auto-generate Markdown documentation with YAML frontmatter for a new feature?▼

To auto-generate Markdown documentation with frontmatter, summarize the module purpose, usage, and navigation metadata. This ensures the YAML frontmatter includes at least name and description, with optional references to scripts, assets, or guides when present.

What is the best way to structure feature docs for different audiences like developers and self-hosters?▼

Structuring feature docs for developers and self-hosters involves applying a standardized template that creates distinct audience sections. This approach ensures navigable and consistent documentation tailored to each technical level.

Can I update existing Markdown documentation to align with code changes?▼

Yes, you can update existing Markdown documentation by aligning it with code changes and existing navigation metadata. This process modifies the current document structure to reflect source context updates while maintaining consistent frontmatter.

Does the documentation generation process support MDX and optional references to scripts?▼

The documentation generation process supports Markdown with YAML frontmatter and includes optional references to scripts, assets, or guides when present. It focuses on generating structured Markdown files rather than processing raw MDX components.

When do I need YAML frontmatter in my feature documentation?▼

You need YAML frontmatter in feature documentation when you require consistent metadata for navigation and discovery. It ensures at least the name and description fields are present, enabling standardized structuring across different audience sections.