Compound

Skill pfeff/claude-skills/skills/compound

Document a solved problem as a searchable solution note in the host's Obsidian vault. Captures a single fix with YAML frontmatter for QMD-based agent discovery; delegates the file write to the obsidian-notes skill.From its SKILL.md

Install

npx -y skills add pfeff/claude-skills --skill compound

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.9 KB, as published. Nobody here has run it

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.