compound-docs

Generate categorized Markdown solution documents with YAML frontmatter.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/compojoom/safe-engineering-plugin --skill compound-docs-compojoom
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: compound-docs
Source: https://github.com/compojoom/safe-engineering-plugin/tree/main/plugins/safe-engineering/skills/compound-docs
Command: npx skills add https://github.com/compojoom/safe-engineering-plugin --skill compound-docs-compojoom

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Documents solved problems as categorized records with YAML frontmatter.

Core Features & Use Cases

  • Auto-create YAML-frontmatter driven docs for each solved issue
  • Organize docs under category directories based on problem_type
  • Centralize knowledge with quick lookup and cross-references

Quick Start

Use the compound-docs skill to capture a recently solved problem and generate a categorized Markdown doc under docs/solutions.

Frequently Asked Questions about compound-docs

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

FAQPage Schema
How do I document solved problems automatically with YAML frontmatter?

You can document solved problems by generating categorized markdown records with YAML frontmatter. The skill creates a single searchable document per issue, organized by problem type and module, enforcing a frontmatter schema for quick lookup.

What is the best way to create a searchable knowledge base from troubleshooting resolutions?

Creating a searchable knowledge base from troubleshooting resolutions involves generating markdown documents per solved issue. Each document is organized under category directories based on problem type and centralized with cross-references for quick lookup.

How does YAML frontmatter organize documentation by problem type?

YAML frontmatter organizes documentation by applying a schema that categorizes each solved issue. Documents are placed under category directories based on problem type, enabling centralized knowledge with quick lookup and cross-references.

Can I use markdown templates to generate documentation for a resolved issue?

Yes, you can use markdown templates to generate documentation for a resolved issue. The skill uses templates from its assets to render the documentation, applying after problem confirmation to capture the solution.

Do I need any dependencies to auto-generate categorized docs for solved issues?

No dependencies are needed to auto-generate categorized docs for solved issues. The skill operates independently, using its internal assets and references to render markdown documents with the required YAML frontmatter schema.

When should I not use automated documentation generation for troubleshooting?

You should not use automated documentation generation before a problem is fully solved and confirmed. The skill applies after problem confirmation to ensure that only valid, completed resolutions are captured as categorized records.