memory-get
SolidRecall long-term memory from Mnemon when GUIDE.md indicates that prior memory may help the current task.
Install
Quality Score: 90/100
Skill Content
Details
- Author
- mnemon-dev
- Repository
- mnemon-dev/mnemon
- Created
- 3 months ago
- Last Updated
- today
- Language
- Go
- License
- Apache-2.0
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
memory-set
Maintain prompt-facing working memory by editing MEMORY.md when GUIDE.md indicates that durable information should be kept.
memex-recall
MUST invoke BEFORE responding to the user's first task message. Your memory is NOT loaded until you run this — the index in system-reminder was removed, you must actively retrieve it.
memory-use
The universal contract for ANY consuming agent using the MemoryVault MCP. Use this skill on every conversation that touches the user's professional context — meetings, customers, decisions, projects, code, anything from their daily work. Establishes when to refer to memory (search first, always), when to give feedback (mem_GAP_* enrichment + memory_update), when to write memory (memory_save discipline + playbooks), and when to escape to a native MCP for deep-dive (parent_surface tells you which source has richer info). Load on every client; the kit's MCP tool descriptions encode the rest.
memory-recall
This skill should be used when the user asks about "past decisions", "previous learnings", "what did we decide", "how did we solve", "remember when", or mentions topics that may have stored memories. Also triggers when working on tasks where historical context would be valuable, such as "working on authentication", "implementing the database", or encountering errors similar to previously resolved issues.
bettermemory
Verification-grade memory between sessions. Use bettermemory's MCP tools (memory_search, memory_show, memory_write, memory_verify, memory_record_use, etc.) instead of writing to files when the user asks you to "remember" something or references shared context from a past session. Default is to NOT call memory_search; only retrieve when the user references context you don't have ("my project", "the script we wrote") or a request is ambiguous in a way stored preferences could resolve. Every hit carries a staleness_verdict (calendar + path-drift + commit-drift); when it isn't "fresh", spot-check a claim before relying and call memory_verify to attest. Every use should record a claim_excerpt so retrievals stay auditable.