Menu
Open the laqrumcode read-only web UI to explore the memory graph (dashboard, memory/concept browsers, graph explorer) in a browser. Use when the user asks to see/visualize/inspect what laqrumcode has stored.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Activate periodically (not per-session) to sample concepts from the graph and verify their claims against current state — code paths, recent sources, user-provided ground truth. Flag stale concepts for supersede-stale. Without this, knowledge rot poisons retrieval silently.
Activate when an insight worth keeping emerges mid-session — a surprising finding, a reusable pattern, a user correction, or a decision with rationale. Use this to write knowledge into the laqrumcode graph immediately rather than waiting for end-of-session daemon extraction (which is batch-only and can have hours of lag).
Activate when the user wants to distill lasting knowledge from ANY source — PDF, web article, pasted text, codebase file, transcript, markdown doc, or book chapter. Source-agnostic replacement for extract-pdf-gems. Same workflow core; source-type-aware quality rules.
Activate when the user asks to extract, mine, distill, or "pull gems" from a PDF, academic paper, book chapter, or research document into the laqrumcode memory graph. Also activate for phrases like "read this paper and remember it", "dense knowledge gems", "pull the insights", or when the user points at a PDF and asks to study it.
Activate when the user asks about state, history, prior work, codebase knowledge, or anything where injected memory should inform the response. Triggers include "what do you know about", "remember", "earlier", "last time", "we discussed", "in this codebase", "prior work", "previously", or any direct question about project/session state.
Activate when the user wants to know what they DO and DON'T know about a topic, before starting research or a project. Turns the graph from a reference library into an active planning tool by reporting coverage and explicit gaps.
| name | laqrumcode-web-ui |
| description | Open the laqrumcode read-only web UI to explore the memory graph (dashboard, memory/concept browsers, graph explorer) in a browser. Use when the user asks to see/visualize/inspect what laqrumcode has stored. |
A local, read-only web UI for exploring the laqrumcode memory graph (GH #15, v1): Dashboard (record counts + embedding coverage), Memory browser, Concept browser, and an interactive Graph explorer.
node scripts/open-ui.mjs
This reads the daemon's auth token (~/.laqrumcode/cache/auth-token) and opens
http://127.0.0.1:<port>/ui in the browser. The default port is
33000 + (uid % 10000) (kept above the daemon's IPC port window); override
with LAQRUMCODE_UI_PORT.
127.0.0.1-only TCP listener, separate
from the Unix-socket hook API.LAQRUMCODE_UI=0 to disable the UI server in the daemon entirely.