enzyme
Enzyme — Vault Exploration Skill
What Enzyme Is
Enzyme turns your Obsidian vault into something you can converse with. It works through three concepts:
Entities are the tags (#travel), wikilinks ([[open questions]]), and folders (/people) in your vault. Each one is a semantic cluster — a gathering of content you've already organized by how you think. Hierarchical tags like #travel/pyrenees create nested clusters.
Catalysts are AI-generated questions anchored to each entity. They probe what's latent in that cluster. A catalyst for #travel might be: "What kept pulling you forward when something was asking you to stay?" — and content surfaces because it speaks to the question, not because it contains matching words. The same entity explored through different catalysts reveals different material.
Petri is the live readout of what's growing in your vault — which entities are active, what catalysts have formed around them, where the thinking is heading. Each entity carries temporal metadata: when you last engaged it, how frequently, whether it's active or dormant. Dormant entities are often the most interesting — they surface threads you've stopped noticing.
Content retrieval works by resonance with catalyst questions, not keyword matching. The catalysts encode the vault's own vocabulary for its themes — they're handles the vault has grown. Reaching for them connects you to content that generic search terms won't find.
Prerequisites
Enzyme resolves the vault path in this order: -p flag > ENZYME_VAULT_ROOT env var > current directory. If ENZYME_VAULT_ROOT is set (check with echo $ENZYME_VAULT_ROOT), all commands automatically target the right vault — no -p or cd needed.