trilium-capturelisted

# Trilium capture Trilium holds what a **human reads**. Ogham holds what an **agent recalls**. Every capture starts by deciding which, and most sessions produce some of each. This skill is conventions only. It calls the tools Trilium's own MCP server already exposes — `search_notes`, `create_note`, `set_attribute`, `append_to_note`, `edit_note_content` — and adds the judgment those tools have no opinion about: where a note goes, what it is called, how it is labelled, and when not to write one at all. ## Requirements The Trilium MCP server must be connected. It is **built into Trilium** (v0.93.0+, mounted at `/mcp`) — do not install or build a third-party one. If the tools are unavailable, say so and put the content in the reply. **A capture skill that silently drops what it was given is worse than no capture skill.** ## Step 1 — Trilium or Ogham? | | goes to Ogham | goes to Trilium | |---|---|---| | shape | a few sentences | a page or more | | consumer | an agent, mid-task | the user, reading | | example | "CAS has been the default git path since 1.1.0" | the full release write-up | | retrieval | `hybrid_search` | browse the tree, or `search_notes` | **When a finding is too long to be an Ogham memory, it is a Trilium note** — and Ogham gets a short memory naming the note. Set `#ogham=yes` on the note so the pairing is visible from both ends. That is the only case where the same material lands in both. A three-sentence gotcha is an Ogham memory even when the user is ta