compound-docs

Document solved problems as categorized YAML-frontmatter entries under docs/solutions.

1|Updated Jan 26, 2026
One-click install
npx skills add https://github.com/AskTinNguyen/vesper-team-skills --skill compound-docs-asktinnguyen
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: compound-docs
Source: https://github.com/AskTinNguyen/vesper-team-skills/tree/main/compound-docs
Command: npx skills add https://github.com/AskTinNguyen/vesper-team-skills --skill compound-docs-asktinnguyen

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Capture solved problems as categorized documentation with YAML frontmatter for fast lookup

Core Features & Use Cases

  • Automatically document solved problems after confirmation to build a centralized, searchable knowledge base.
  • Organize docs by problem_type into category directories with structured YAML frontmatter and references.
  • Provide a quick-start workflow to generate documented entries and cross-reference related issues.

Quick Start

Run the documentation workflow after solution verification to generate a categorized doc.

Frequently Asked Questions about compound-docs

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

FAQPage Schema
How do I automatically document solved problems with YAML frontmatter for quick lookup?▼

Automatically document solved problems by running a documentation workflow after solution verification to generate categorized entries. The system stores each entry under docs/solutions with structured YAML frontmatter, code snippets, and cross-references for fast retrieval.

What is the best way to build a searchable knowledge base from solved coding issues?▼

Build a searchable knowledge base by categorizing documented solutions by problem type into category directories. Each entry includes validated YAML frontmatter metadata, prevention guidance, and cross-references to ensure related issues are easily discoverable.

Does the documentation workflow validate YAML frontmatter against a schema?▼

Yes, the documentation workflow validates YAML frontmatter against a schema.yaml file. This ensures that all generated entries include searchable metadata, cross-references, and prevention guidance before being stored in the knowledge base.

How do I generate categorized documentation entries with cross-references and code snippets?▼

Generate categorized documentation entries by running the workflow after confirming a solution. The system applies a structured template that automatically incorporates code snippets, cross-references, and prevention guidance into the final documented entry.

Can I organize documentation by problem type into category directories?▼

Yes, you can organize documentation by problem type into category directories. The workflow automatically categorizes each documented solution and stores it under docs/solutions using a structured template for centralized management.

What limitations exist when using YAML frontmatter for automated knowledge base documentation?▼

The documentation process requires YAML frontmatter to strictly validate against the defined schema.yaml. Entries lacking proper metadata, cross-references, or prevention guidance will fail validation and not be stored in the knowledge base.