Loading...
Loading...
Found 5 Skills
Use the Trove hosted memory graph (MCP server "trove") to recall prior work, decisions, preferences, and system knowledge before re-deriving them, and to save durable new facts back. Trigger whenever a question touches past projects, "how does my setup work", preferences, decision history, or when a session produces a decision or fact worth remembering. Routes to the trove-recall, trove-remember, trove-ingest, and trove-lint skills; the mcp__trove__* tools (remember, recall, grep, read, connect, forget) are the interface.
Use to health-check the Trove memory graph - orphan nodes, missing evidence, duplicate titles, dangling edges. Interprets lint findings, separates real issues from noise, and proposes fixes (linking passes, evidence backfill, merges) without auto-applying them.
Save durable knowledge into the Trove memory graph — new facts, decisions, gotchas, AND corrections to known facts. Replaces the old trove-capture and trove-update skills; the remember tool handles create-vs-revise itself. Trigger after a session produced insight worth keeping, when the user states a fact or preference to remember, or when a known fact changed (PR merged, port moved, X replaced Y).
Use when a question should be answered from the Trove memory graph rather than re-derived - prior projects, decisions, system knowledge, preferences, "what was I working on". Routes grep → read → recall by query shape (exact string, known slug, open question), synthesizes with citations, and remembers non-trivial answers back so exploration compounds.
Use when the user shares a source (URL, file path, paste, transcript) that should be indexed into the Trove memory graph. Stores the raw evidence first via ingest, then remembers semantic atoms citing exact text units.