compound-docs

Generate categorized Markdown entries with YAML frontmatter for solved problems.

Updated Mar 3, 2026
One-click install
npx skills add https://github.com/The-Rabak/naysmith --skill compound-docs-the-rabak
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: compound-docs
Source: https://github.com/The-Rabak/naysmith/tree/main/.github/skills/compound-docs
Command: npx skills add https://github.com/The-Rabak/naysmith --skill compound-docs-the-rabak

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Automatically document solved problems to build searchable institutional knowledge with category-based organization (enum-validated problem types).

Core Features & Use Cases

  • Automatic documentation creation for solved problems with categorized markdown entries
  • YAML frontmatter metadata for fast lookup and cross-reference
  • Pattern detection for related issues and reuse in future sessions

Quick Start

Invoke the documentation workflow after a problem is confirmed solved 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 automate documenting solved problems with YAML frontmatter?

You can document solved problems by invoking a workflow that automatically generates categorized Markdown entries with YAML frontmatter. This process validates metadata against a YAML schema and stores entries under structured category directories for searchable institutional knowledge.

What's the best way to organize a knowledge base of problem-solving solutions?

Organize a solutions knowledge base by categorizing Markdown entries by problem type with enum-validated YAML frontmatter. Files are stored under structured category directories, enabling fast cross-referencing and pattern detection for related issues during future lookup.

How does cross-reference generation work for categorized Markdown documentation?

Cross-reference generation for categorized Markdown works by validating YAML frontmatter against a predefined schema and applying pattern detection. This mechanism automatically links related problem-solving entries stored across different category directories within the knowledge base.

Can I validate YAML frontmatter against a schema when creating problem-solving documentation?

Yes, YAML frontmatter can be validated against a schema when creating problem-solving documentation. This ensures metadata consistency across categorized Markdown entries, allowing reliable cross-referencing and accurate pattern detection for future lookup sessions.

When do I need to generate pattern detections for a documentation knowledge base?

You need pattern detections when building a searchable knowledge base from solved problems to identify related issues. This mechanism analyzes categorized Markdown entries with YAML frontmatter to surface reusable solutions and detect recurring patterns across different categories.