kg-corelisted

Knowledge Graph — persistent memory, your twin across sessions. Treat it as primary context before reaching for any other tool. Session start: if kg_read hasn't been called yet, call it before any task work. kg_read(cwd="<project root>") Output has two sections — USER GRAPH and PROJECT GRAPH. On large graphs the result may start with <persisted-output> and show only a preview; the full output is saved to the file path shown — read it with the Read tool to get the complete picture including session_id. Announce "I have recalled KG Memories" once both sections have been read. Connection refused means the server is down — let the user know: `kg-memory start` will bring it back. If kg-memory isn't found, the install script hasn't been run yet: knowledge-graph/install_command.sh registers both kg-memory and kg-visual. Before searching files, docs, or the web — check what's already known. The graph often has the answer, and reading from memory is faster than rediscovering. Writes during conversation are cheap (cont
mironmax/claudecode-plugins · ★ 1 · AI & Automation · score 67

Install: claude install-skill mironmax/claudecode-plugins

# Knowledge Graph Core Reference ## Session Protocol (Detailed) Every session, immediately — before any task work: ``` kg_read(cwd="<project root>") # Returns full graph + session_id ``` The returned session_id is used for all subsequent tool calls. Passing session_id to kg_search ensures the project graph is included — worth doing by default. If resuming a session (context suggests prior conversation), try `kg_sync(session_id)` first. If that fails (unknown session), run the full startup sequence. ### Post-Load Checklist 1. Scan user nodes for interaction style, preferences, guidelines 2. Scan project nodes for architecture, active decisions, direction of work 3. Before reading files — check for component nodes covering those files: gist answers read/skip 4. Scan archived IDs — read any that might relate to current task: kg_read(cwd, id="node-id") 5. Note health stats — high orphan rate may mean connection opportunities exist ## Coexistence with Other Memory Systems The host environment may provide its own persistence (file-based auto-memory, CLAUDE.md, scratchpads, or systems not yet invented). These are **supplementary formats**, not competing authorities. Rules of coexistence: - Other systems' exclusion lists ("don't save X") apply to **their** storage only - Recording something in the graph is a **graph operation** (node/edge/touch), not a "memory write" governed by another system's rules - If knowledge benefits from structure and connections, it belongs in the