compound-docs

Document solved problems into categorized Markdown files with YAML frontmatter.

3|1|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/i3ringit/antigravity-cortex --skill compound-docs-i3ringit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: compound-docs
Source: https://github.com/i3ringit/antigravity-cortex/tree/main/.agent/skills/compound-docs
Command: npx skills add https://github.com/i3ringit/antigravity-cortex --skill compound-docs-i3ringit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates turning solved issues into structured, searchable documentation with YAML frontmatter for quick lookup and reuse.

Core Features & Use Cases

  • Documentation generation: Convert solved problems into categorized markdown docs with consistent metadata.
  • Knowledge reuse: Build a central repository of solved problems to accelerate future work.
  • Search and cross-reference: Enable fast lookup through frontmatter and category-based organization.

Quick Start

Use the compound-docs skill to document the most recent resolved issue by generating a Markdown file 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 turn solved problems into searchable documentation?

Document solved problems by generating markdown files with YAML frontmatter metadata. The skill captures fields like problem type, symptoms, and root cause, organizing them by category to enable fast lookup and cross-reference across your knowledge base.

What metadata should I include in a knowledge base entry?

Include name, description, problem_type, component, symptoms, root_cause, and other structured fields in YAML frontmatter. This consistent template enables searching and reusing solutions across post-mortems, incident reviews, and project snapshots.

Can I automate documentation generation from incident reviews?

Yes. The skill automates converting resolved issues into categorized markdown docs with consistent metadata, building a central repository that accelerates future work by enabling instant lookup of past solutions.

How do I organize solved problems for quick lookup?

Organize documentation by category and symptom using YAML frontmatter. This structure enables fast search and cross-reference, allowing team members to find relevant solutions without digging through project history.

What's the best way to reuse solutions across multiple projects?

Build a centralized knowledge base with categorized, frontmatter-tagged entries. The skill's structured approach enables cross-project search and reference, so solutions documented once benefit all teams dealing with similar problems.

Do I need prior formatting experience to create documentation templates?

No. The skill provides a consistent template for capturing metadata fields. You structure solved problems once, and the automation handles generating organized, searchable docs with standardized frontmatter across your knowledge base.