compound-docs

Document solved problems as structured Markdown files with YAML frontmatter metadata.

Updated Feb 16, 2026
One-click install
npx skills add https://github.com/praburajasekaran/ruthva-clinic-os --skill compound-docs-praburajasekaran
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: compound-docs
Source: https://github.com/praburajasekaran/ruthva-clinic-os/tree/main/.gemini/skills/compound-docs
Command: npx skills add https://github.com/praburajasekaran/ruthva-clinic-os --skill compound-docs-praburajasekaran

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the documentation of solved problems, creating a searchable knowledge base for future reference and institutional learning.

Core Features & Use Cases

  • Automated Documentation: Captures and documents solved problems immediately after confirmation.
  • Structured Documentation: Uses YAML frontmatter for metadata and searchability.
  • Use Case: After solving a complex issue, the skill automatically generates a structured document that includes all necessary details for future reference.

Quick Start

Use the compound-docs skill to document the solution to the problem you just solved.

Frequently Asked Questions about compound-docs

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

FAQPage Schema
How do I automate documentation of solved problems for institutional knowledge?

Automate documentation of solved problems by capturing context and validation inputs to generate structured markdown files with YAML frontmatter, building a searchable knowledge base for institutional learning and future reference.

What is YAML frontmatter and how does it make problem documentation searchable?

YAML frontmatter is metadata embedded at the top of markdown files that structures solved problem details into searchable fields, enabling automated knowledge base retrieval and institutional learning.

How do I create a searchable knowledge base from solved technical issues?

Create a searchable knowledge base by documenting solved problems immediately after confirmation using structured markdown with YAML frontmatter, ensuring all necessary details are captured for future reference.

Does automated problem documentation require manual input for context and validation?

Automated problem documentation requires user input for context and validation, while automating filename generation and YAML schema validation to ensure structured markdown files are accurately created.

What's the best way to capture institutional learning from complex solved issues?

Capture institutional learning by using automated documentation tools that generate structured markdown files with YAML frontmatter immediately after a complex issue is solved and confirmed, ensuring details are preserved for future reference.

Are there limitations to automating knowledge base creation with YAML frontmatter?

Automating knowledge base creation with YAML frontmatter is limited by its dependency on user input for context and validation, meaning it cannot autonomously document unsolved or unconfirmed problems.