菜单
Selectively and REVERSIBLY forget stored memories/concepts (privacy / declutter) — soft-deactivate content matching a query or date so it stops surfacing in retrieval. Use when the user wants sensitive or unwanted data out of their laqrumcode graph.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
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-forget |
| description | Selectively and REVERSIBLY forget stored memories/concepts (privacy / declutter) — soft-deactivate content matching a query or date so it stops surfacing in retrieval. Use when the user wants sensitive or unwanted data out of their laqrumcode graph. |
Soft-forget content so it stops surfacing in retrieval. Honors the D4 founder
rule — nothing is deleted; matching rows are soft-deactivated with an audit
annotation (archive_reason='forget:…') and can be fully reactivated.
node scripts/forget.mjs --query "api key" # preview (DRY RUN)
node scripts/forget.mjs --query "api key" --commit # apply
node scripts/forget.mjs --before 2026-01-01 --commit # forget content older than a date
node scripts/forget.mjs --undo --commit # reactivate everything forgotten by this tool
--commit to apply.status='archived'; concept → superseded_at set — both with
archive_reason='forget:…'. The retrieval pipeline already excludes these, so
they stop surfacing immediately, with no change to the hot retrieval path.--undo --commit reactivates everything this tool forgot.--query (case-insensitive substring) and --before (ISO date).memory + concept (the content tables whose retrieval candidate
query already filters the deactivation flag).--project / --session (edge-scoped) and never-remember
redaction at ingestion (privacy.json).SURREAL_URL/USER/PASS/NS/DB (same defaults as backup).