skills.rest
Andreicr1
Andreicr1COMMUNITY
Explore all skills by this author →
GitHub

compound-docs

Generate YAML frontmatter-enabled Markdown files for solved problems in docs/solutions.

Updated Aug 23, 2026
Search Tags:#templates#documentation#problem-solving#yaml-frontmatter#knowledge-base#cross-references#docs-automation
One-click install
npx skills add https://github.com/Andreicr1/Netz-Private-Credit-OS --skill compound-docs-andreicr1
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: compound-docs
Source: https://github.com/Andreicr1/Netz-Private-Credit-OS/tree/main/.github/skills/compound-docs
Command: npx skills add https://github.com/Andreicr1/Netz-Private-Credit-OS --skill compound-docs-andreicr1

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Captures solved problems and converts them into categorized Markdown documentation using YAML frontmatter, enabling fast lookup and consistent knowledge sharing across teams.

Core Features & Use Cases

  • Automatically generate a category-aligned document for each solved problem, with standardized frontmatter for discovery and searchability.
  • Centralize institutional knowledge to improve onboarding, debugging, and AI-assisted sessions.
  • Use case: after solving an issue, generate a structured doc in docs/solutions/[category]/[filename].md detailing problem, root cause, solution, and prevention.

Quick Start

Document a solved problem by creating a category-based Markdown file with YAML frontmatter in 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 auto-generate documentation for solved problems using YAML frontmatter?▼

To document solved problems, create a category-based Markdown file with YAML frontmatter in docs/solutions/[category]/[filename].md. This structured approach captures the problem, root cause, solution, and prevention details for fast lookup.

What is the best way to structure a searchable knowledge base for debugging solutions?▼

Building a searchable knowledge base of debugging solutions requires YAML frontmatter-enabled Markdown files stored in category-based directories. This enforces enum-driven problem_type categorization and generates cross-references for related issues.

Can I use enum-driven categorization for problem types in Markdown documentation?▼

Yes, enum-driven categorization for problem types is supported in Markdown documentation. The system enforces enum-driven problem_type categorization and validates the YAML frontmatter against a defined schema for consistent categorization.

How do I validate YAML frontmatter against a defined schema for docs automation?▼

YAML frontmatter is validated against a defined schema during docs automation. This ensures generated Markdown files meet the required structure, link to relevant templates and patterns, and produce accurate cross-references for related issues.

Does this docs automation approach work without external dependencies?▼

Yes, this docs automation approach works without external dependencies. It independently generates structured Markdown documentation, validates frontmatter schemas, and stores artifacts in the docs/solutions directory for fast lookup.

Related Skills

Explore More Content & Communication Skills→
CristoVenturesCristoVentures
2

compound-docs

Generate categorized Markdown files with YAML frontmatter for solved problems.

Official
Intermediate
hve4638hve4638

wiki

Store and retrieve persistent project knowledge in a markdown wiki.

Community
Advanced
constellizeconstellize
1

create-knowledge-contribution

Package personal insights into structured team knowledge contributions with templates.

Official
Advanced
MadBomberMadBomber
11

compound-docs

Captures solved technical problems and generates categorized Markdown documents with validated YAML frontmatter.

Community
Advanced