paper-glossary

Provide the paper's source manifest JSON to the proposal script, review the numbered candidate shortlist it presents, then select terms by number. The skill triages, inventories, writes, and optionally links the selected terms in your configured vault glossary directory.

Run configure_glossary.py with --terms-dir pointing to a directory inside an Obsidian vault containing a .obsidian folder. This writes a device-local config at ~/.paper-glossary/config.json that later runs reuse automatically.

No, existing notes are never replaced. Thin notes receive only missing structured fields and a missing occurrence, complete notes receive at most a missing occurrence, and all writes pass a whole-batch preflight before commit.

Yes, when you supply an explicit article Markdown path in the same vault, the linker inserts one first-safe-occurrence wiki link per term. It skips code blocks, headings, existing links, and reference sections, and verifies the article hash before modifying it.

The workflow reports a no_candidates terminal state and stops without displaying an empty selector. No glossary notes or article Markdown are written in that case.

Each stage recomputes the proposal, review, and selection digests against the current source manifest and saved artifacts. Any mismatch in paper ID, source hash, term order, or surface forms causes a fail-closed rejection to prevent unauthorized writes.