compound-docs

Generate categorized Markdown documents with YAML frontmatter for solved problems.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/CuriousCrow123/godot-compound --skill compound-docs-curiouscrow123
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: compound-docs
Source: https://github.com/CuriousCrow123/godot-compound/tree/main/skills/compound-docs
Command: npx skills add https://github.com/CuriousCrow123/godot-compound --skill compound-docs-curiouscrow123

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) and references (resource) components.

What problem does it solve?

This skill automates documenting solved problems into a centralized, categorized knowledge base, enabling fast lookup and consistent record-keeping.

Core Features & Use Cases

  • Automatically generate a structured Markdown document per solved problem, stored under docs/solutions.
  • YAML frontmatter metadata and search-friendly structure.
  • Cross-referencing related issues and templates from assets.

Quick Start

Run the documentation workflow after solving a problem to generate a categorized, YAML-frontmatter document.

Frequently Asked Questions about compound-docs

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

FAQPage Schema
How do I automatically generate Markdown documentation for solved problems?

Automatically generate Markdown documentation by running the workflow after solving a problem, which creates a structured document with YAML frontmatter stored under docs/solutions. It categorizes the file and validates metadata against the schema for consistent record-keeping.

What is the best way to organize a knowledge base with YAML frontmatter and cross-references?

Organize a YAML frontmatter knowledge base by categorizing Markdown documents under docs/solutions. The process includes cross-referencing related issues and templates from assets to ensure fast lookup and validated metadata consistency.

Does this documentation workflow require any specific templates or schema files to run?

Yes, the documentation workflow requires access to assets/templates and the YAML schema to format and validate the generated documents. These components ensure the output metadata remains consistent across the categorized knowledge base.

Can I use YAML frontmatter to validate metadata consistency across a categorized docs folder?

Yes, you can validate metadata consistency across a categorized docs folder by checking the generated YAML frontmatter against the required schema. This ensures every solved problem document remains structured and searchable.

How do I cross-reference related issues and templates in Markdown documentation?

Cross-reference related issues and templates by pulling from the assets directory during the document generation workflow. This automatically links relevant templates and issues within the categorized Markdown file's structure.

What are the limitations of relying on YAML frontmatter for problem documentation?

Relying on YAML frontmatter for problem documentation requires strict schema validation and pre-existing assets/templates. If the schema is not enforced or templates are missing, the categorized knowledge base loses its consistency and searchability.