intent-memory
Memory evidence retrieval
Retrieve only when prior context would change the answer and is missing. Skip self-contained tasks and use already available sources directly. When the user names a current document or business system as authoritative, inspect it; historical memory cannot override current evidence.
Use the host's normal tools throughout. Known session IDs, paths, dates, and quotations often need only exact search or a source read. Use intentgrep to find useful material by meaning when the wording is unknown. A keyword prefilter is optional, and this skill does not require semantic searches for every step.
Keep instruction files, curated summaries, original conversations, and live state distinct. A proposal is not approval, an attempted call is not success, and a relevance score is not permission.
Tool setup and task choice
The Skill is installed independently from the repository; it does not install a CLI, provider, hooks, scheduling, or a memory database. Check intentgrep --help when needed. For first use, run npx --yes --package=@shareai-lab/intentgrep@0.1.0 intentgrep --help; repeated use can use an authorized global install or project dependency. A reviewed local tarball is also supported. Treat missing CLI/key as an unavailable search, not as no memory.
Use --task search --profile memory for finding evidence. Approval, refusal, deferral, and later reversal can all help answer “was this authorized?” The query need not be a condition each returned record proves alone.
Use --task filter only for explicit record selection, such as “the record quotes a user confirmation.” Filtering for confirmation alone can hide counterevidence. Neither mode settles authority; read the original span with speaker, time, and outcome before synthesis. Extra --instructions can express the current evidence question without replacing the scoring protocol.
Default text units are lines. For transcripts where speaker or outcome sits nearby, use --context-lines N or a suitable explicit --unit paragraph|window. -A/-B/-C only changes displayed output; it does not give that context to the model. JSONL records should already contain the relevant source span and permitted metadata.