cognitive-memory

Store, search, and curate lasting facts in a node-based cognitive memory map.

33|1|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/infinition/LaRuche --skill cognitive-memory-infinition
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cognitive-memory
Source: https://github.com/infinition/LaRuche/tree/main/laruche/skills/cognitive-memory
Command: npx skills add https://github.com/infinition/LaRuche --skill cognitive-memory-infinition

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Everything an agent learns disappears at the end of a turn unless it is written down. This Skill provides the operational discipline for persisting facts about users, projects, and decisions into a structured memory map, finding them again reliably, and keeping the map from degrading into noisy, duplicated clutter. ## Core Features & Use Cases - Structured fact storage: Write one fact per call into dotted, snake_case node ids (e.g., projects.laruche), with absolute dates and sources, using memory_write after checking for existing entries with memory_search and memory_suggest_nodes. - Retrieval workflows: Orient before any task with memory_search, read whole nodes with memory_read_node, find literal strings with memory_grep, and inspect the map shape with memory_tree. - Map curation: Diagnose overload with memory_doctor, merge bloated nodes with memory_consolidate, move or delete stale items with reasons, and review pending proposals via memory_list_proposed and memory_review. - Use Case: A user mentions they chose the MPL-2.0 license for their project. The agent searches memory first, finds no existing entry, writes the decision with its date and rationale to decisions.licence_mpl, and confirms the write by re-reading the node. ## Quick Start Ask the agent to remember a specific fact about your project or preferences, and it will search for duplicates, pick the right memory node, and store it permanently.

Frequently Asked Questions about cognitive-memory

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I make an AI agent remember facts across sessions?▼

Write each fact to the cognitive memory map with memory_write, providing a node_id and content. Search first with memory_search to update existing items instead of duplicating them, and use absolute dates so the fact stays meaningful later.

Should I store documents in agent memory or as files?▼

Store reference documents as files on disk, then write one memory item pointing to the file path with a one-line description. Memory holds facts about the user and work; dumping full documents into memory pollutes every future search with noise.

Why does memory search return irrelevant or duplicate results?▼

This happens when too few nodes hold too many items, or when facts were written repeatedly instead of updated. Run memory_doctor to find overloaded nodes, consolidate them with memory_consolidate, and delete duplicate items while keeping the most complete one.

What is the difference between memory_search and memory_grep?▼

memory_search is semantic and finds conceptually related items, while memory_grep matches literal strings such as exact paths, tokens, or ids. If a semantic search returns nothing, try memory_grep with a literal fragment before concluding the fact was never stored.

Can I store API keys or passwords in agent memory?▼

No. Memory items are read back into prompts, which means they flow into provider requests and logs. Secrets such as API keys, tokens, and passwords belong in a dedicated secrets vault, never in a memory item.