Memory Proactive
Proactive layered recall and generic domain-aware routing.
Get the complete skill folder, including its scripts and reference files.
This page is available to readers but is excluded from the public index, because it does not yet meet the evaluation standard.
When to use this skill
Use Memory Proactive when an AI agent needs a reusable SKILL.md workflow for this job: Proactive layered recall and generic domain-aware routing.
When not to use it
Skip Memory Proactive when the task is outside the coding category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/memory-proactive # Save SKILL.md to ~/.claude/skills/memory-proactive/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/memory-proactive/SKILL.md. For a shared project, commit the folder at .claude/skills/memory-proactive/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Memory Proactive skill for this task: Use Memory Proactive when this documented workflow matches the task. Confirm any required inputs or files before making changes.
What supports this recommendation?
66/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 64/100
- Practical detail
- 68/100
- Source evidence
- 61/100
- Source signals
- 72/100
Model compatibility evidence
- claudeuntested
No model-specific signal or recorded compatibility test was found.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# Memory Proactive
This skill describes the current proactive recall surfaces that remain useful in the local repository.
## Layered Context Injection
Primary engine: `tiered_context_injector.py`
It combines multiple recall paths before the next interaction:
- recent session recall from shared SQLite state - governance-backed object and hub recall - knowledge note recall - optional live Hindsight recall when the query profile needs it
Example:
```bash python3 scripts/tiered_context_injector.py --query "user preferences" ```
Useful knobs:
- `--min-score 0.3` - `--max-results 10` - `--recall "project status" "system config"` - `--domains project,stock`
## Generic Domain Routing
Helper: `domain_memory.py`
This is a lightweight legacy helper for splitting local memory into generic domains so one topic does not crowd out everything else.
Example domains:
- `project` - `stock` - `system` - `marketing` - `relationship` - `general`
Example:
```bash python3 scripts/domain_memory.py check project "Milestone planning note" python3 scripts/domain_memory.py status ```
## Guidance
- use generic domains, not user- or project-specific hardcoded labels - keep recall queries portable across agent runtimes - treat this skill as an optional helper layer, not a required production contract
Intended uses
- Use Memory Proactive when this documented workflow matches the task.
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.