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.
Activate when user mentions "search memory", "recall", "remember", "core memory", "introspect", "memory status", "what did we do", "past sessions", "identity", "soul", or when you need to store/retrieve persistent knowledge across sessions.
Activate when the user wants to export laqrumcode for import into a non-SurrealDB system — Postgres + pgvector, Neo4j, OpenSearch, a custom store, or any system that ingests JSON. Triggers on "export laqrumcode to JSON", "dump laqrumcode for ingestion", "migrate laqrumcode off SurrealDB". Use this skill when the destination is not SurrealDB; for SurrealDB-to-SurrealDB use `laqrumcode-backup-native`.