Compound Skill

Captures a solved problem as a type=reference note in the host's Obsidian vault, using the vault's real frontmatter convention. Notes are discovered by future agents via QMD hybrid search (BM25 + vector + reranker) over the vault.

Core Concepts

Single-problem focus: Unlike /claude-skills:lessons-learned (session retrospective), /claude-skills:compound documents one solved problem at a time. Lightweight, focused, fast.

Vault-resident: Notes live in the Obsidian vault, not in any repository's docs/. The actual file write is delegated to the obsidian-notes skill (CLI-first); vault location is resolved per-host from ~/.claude/hosts/<hostname>.md.

Schema: Solution notes use the vault's real note convention — there is no dedicated Solution template or problem_type frontmatter field in the vault. Notes are written as type=reference (the closest existing note type). Problem classification (build-error, severity, etc.) is captured as tags, not invented frontmatter keys. See Integration Points below for the property list and operations/document-solution.md for the full field mapping.

Invocation

/claude-skills:compound                          # Interactive — asks what you solved
/claude-skills:compound timeout in auth flow     # Pre-seeded with problem context

Execution

When this skill is invoked:

Step 1: Load operation details

Read(file_path: "${CLAUDE_PLUGIN_ROOT}/skills/compound/operations/document-solution.md")

Step 2: Execute the operation interactively

Step 3: Report the created note path in the vault

Operations

Document Solution (Default)

File: operations/document-solution.md When: User invokes /claude-skills:compound to capture a solved problem.

Quick summary: Gather problem context, generate frontmatter, write a type=reference note via the obsidian-notes skill using the vault's real properties (area/project/status/date/tags/keywords, set explicitly via property:set — no template).

Output

Creates a solution note at:

<vault>/Notes/<YYYY>/<MM>/<YYYY-MM-DD>-<slug>.md

<vault> is resolved by the obsidian-notes skill from the host config.

Integration Points

• Vault Reference template: <vault>/Templates/Reference.md — the note type compound builds on; frontmatter schema is the vault's standard type/area/project/status/date/tags (plus the real, registered keywords field). Body sections (Problem, Symptoms, Root Cause, Solution, Prevention) are caller-composed, not template-defined.
• Obsidian-notes skill: ~/.claude/skills/obsidian-notes/SKILL.md — CLI surface (create, property:set, append) used for the write, plus the non-blocking failure contract.
• Host config: ~/.claude/hosts/<hostname>.md ## Obsidian section — vault path, CLI binary.
• Retrieval: QMD hybrid search over the vault — skills/task-workflow/references/solution-search.md defines the canonical query protocol used by init-workspace, planning-workflow, and other read-side callers.
• Lessons-learned bridge: Phase 3d of /claude-skills:lessons-learned may invoke /claude-skills:compound for problems with concrete, reusable fixes.

See Also

• /claude-skills:lessons-learned — Session retrospective; bridges to /claude-skills:compound for concrete fixes.
• /claude-skills:self-improvement — Apply recommendations to skills.
• obsidian-notes skill — CLI surface for vault writes.