Kb compile

Skill pfeff/claude-skills/skills/kb-compile

Compile staged knowledge-base sources into the vault's native notes: one per-source summary (type: reference) plus fuller concept notes (type: zettel) in Notes/, cross-linked to Keywords/ term pages and surfaced through a KB MOC + Dataview. Incremental and idempotent; concept notes update in place. Bounded writes (never DevOps Documentation//Confluence/ or unrelated notes); edit safety is git + review. Operator-invoked via /kb-compile. Use when turning raw/ sources into linked, queryable knowledge.From its SKILL.md

Install

npx -y skills add pfeff/claude-skills --skill kb-compile

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.3 KB, as published. Nobody here has run it

KB Compile

The core behavior of the LLM Knowledge Base workflow (SPEC v2 §2.2). Incrementally compiles un-compiled sources from the vault's raw/ queue into the vault's existing note idioms — type:-routed notes in Notes/, cross-linked into Keywords/ and the MOC/Dataview machinery.

Status: the deterministic primitives are implemented and unit-tested in kb-core (source_key, is_writable, concept_slug, TYPE_*). Summarization, concept extraction, and the writes are agent-orchestrated per operations/compile.md.

Billing posture

/kb-compile is operator-invoked and interactive → subscription billing pool. It must never be wired to cron, claude -p, or the Agent SDK (that moves the workflow to the metered pool; requires operator sign-off). See SPEC v2 §6 and the CLAUDE.md billing guard.

What it writes (SPEC v2 §2.2)

Source summary → Notes/YYYY/MM/ (type: reference, project: knowledge-base, sources: [<key>]): one summary note per source.
Concept notes → Notes/YYYY/MM/ (type: zettel): fuller-than-keyword treatments; created new or updated in place (dedup by concept_slug) on re-compile.
Keywords/ cross-link: concept notes [[link]] to term pages; compile may create a new Keywords/ stub or elaborate an existing one (free-edit, git-reviewable).
KB MOC (type: moc) with a Dataview block over the KB notes; backlinks summary ↔ concept ↔ keyword.

Bounded writes: never DevOps Documentation//Confluence/ or notes outside the compile's scope (kb_core.is_writable floor + task-scope). Incremental/idempotent (AC-2.2). Every note carries type: + sources: (INV-2/INV-3). No fence — edit safety is git + review (INV-5).

Invocation

/kb-compile               # compile all uncompiled raw/ sources

Execution

Load the operation: Read(${CLAUDE_PLUGIN_ROOT}/skills/kb-compile/operations/compile.md)
Execute it.
Report summaries written, concept notes created/updated, Keywords/ pages touched, and sources compiled.

Integration Points

kb-core — ${CLAUDE_PLUGIN_ROOT}/skills/kb-core/scripts/kb_core.py (source_key, is_writable, concept_slug, KB_PROJECT, TYPE_*).
obsidian-notes skill / host config — vault path resolution + writes.
kb-capture — fills the raw/ queue this skill drains.
kb-lint — health-checks the KB notes this skill produces.