Content & Documentation Generator

Generate Markdown, MDX, or HTML docs from OpenAPI specs or content briefs.

6|Updated Oct 25, 2025
One-click install
npx skills add https://github.com/williamzujkowski/cognitive-toolworks --skill content-documentation-generator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Content & Documentation Generator
Source: https://github.com/williamzujkowski/cognitive-toolworks/tree/main/skills/documentation-content-generator
Command: npx skills add https://github.com/williamzujkowski/cognitive-toolworks --skill content-documentation-generator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Technical documentation, API references, and content creation can be time-consuming; this Skill automates production of well-structured, accessible docs with SEO considerations.

Core Features & Use Cases

  • Generate Markdown/MDX documentation from templates and content briefs
  • Create API documentation from OpenAPI specifications
  • Produce documentation site-ready structures with frontmatter and metadata
  • Use Case: teams needing consistent, accessible docs across APIs and products

Quick Start

Provide a content brief or an OpenAPI spec to generate docs instantly.

Frequently Asked Questions about Content & Documentation Generator

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

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

To generate API documentation from an OpenAPI spec, provide the specification to the generator. It validates the input and automatically produces structured, accessible API references complete with frontmatter metadata in markdown, mdx, or html outputs.

Can I create markdown documentation that includes SEO metadata and frontmatter?

Yes, you can create markdown documentation with SEO metadata and frontmatter. The generator automatically produces frontmatter containing title, description, keywords, and a generated_at timestamp to ensure content is ready for documentation sites.

What is the best way to ensure technical guides meet accessibility standards?

The best way to ensure technical guides meet accessibility standards is by using an automated documentation generator that enforces accessibility rules during creation. It processes your content briefs and outputs accessible markdown or html structures.

Does this documentation generator support mdx output for knowledge bases?

Yes, this documentation generator supports mdx output for knowledge bases. It can produce documentation site-ready structures with frontmatter and metadata in markdown, mdx, and html formats from your content briefs.

Do I need a specific style guide to automate technical docs creation?

You do not need a specific external style guide to automate technical docs creation. The generator enforces a selected style guide during processing, applying consistent formatting and structure to your API references and content briefs.