Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Infinite organized memory that complements your agent's built-in memory with unlimited categorized storage.
Infinite organized memory that complements your agent's built-in memory with unlimited categorized storage.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Superpowered memory that never forgets. Your agent has basic built-in memory. This skill adds infinite, perfectly organized memory for everything else β parallel and complementary, never conflicting.
Built-in Agent Memory This Skill (~/memory/) βββββββββββββββββββββββ βββββββββββββββββββββββββββββββ β MEMORY.md β β Infinite categorized storage β β memory/ (daily logs)β + β Any structure you want β β Basic recall β β Perfect organization β βββββββββββββββββββββββ βββββββββββββββββββββββββββββββ β β Agent basics Everything else (works automatically) (scales infinitely) Not a replacement. Your agent's built-in memory keeps working. This adds a parallel system for unlimited, organized storage.
On first use, read setup.md to configure the memory system with the user. Key decisions: What categories do they need? Should we sync anything from built-in memory? How do they want to find things?
User needs organized long-term storage beyond basic agent memory: detailed project histories, extensive contact networks, decision logs, domain knowledge, collections, or any structured data that grows over time.
Memory lives in ~/memory/ β a dedicated folder separate from built-in agent memory. ~/memory/ βββ config.md # System configuration βββ INDEX.md # What's stored, where to find it β βββ [user-defined]/ # Categories the user needs β βββ INDEX.md # Category overview β βββ {items}.md # Individual entries β βββ sync/ # Optional: synced from built-in memory βββ ... The user defines the categories. Common examples: projects/ β detailed project context people/ β contact network with full context decisions/ β reasoning behind choices knowledge/ β domain expertise, reference material collections/ β books, recipes, anything they collect See memory-template.md for all templates.
TopicFileFirst-time setupsetup.mdAll templatesmemory-template.mdOrganization patternspatterns.mdProblems & fixestroubleshooting.md
This system lives in ~/memory/. Never modify: Agent's MEMORY.md (workspace root) Agent's memory/ folder (if it exists in workspace) Parallel, not replacement. Both systems work together.
During setup, ask what they want to store. Create categories based on their needs: They say...Create"I have many projects"~/memory/projects/"I meet lots of people"~/memory/people/"I want to track decisions"~/memory/decisions/"I'm learning [topic]"~/memory/knowledge/[topic]/"I collect [things]"~/memory/collections/[things]/ No preset structure. Build what they need.
Each folder gets an INDEX.md that lists contents: # Projects Index | Name | Status | Updated | File | |------|--------|---------|------| | Alpha | Active | 2026-02 | alpha.md | | Beta | Paused | 2026-01 | beta.md | Total: 2 active, 5 archived Indices stay small (<100 entries). When full, split into subcategories.
When user shares important information: Write to appropriate file in ~/memory/ Update the category INDEX.md Then respond Don't wait. Don't batch. Write immediately.
To find information: Ask first: "Is this in ~/memory/ or built-in memory?" Search: grep or semantic search in ~/memory/ Navigate: INDEX.md β category β specific file # Quick search grep -r "keyword" ~/memory/ # Navigate cat ~/memory/INDEX.md # What categories exist? cat ~/memory/projects/INDEX.md # What projects? cat ~/memory/projects/alpha.md # Specific project
If user wants certain info copied from built-in memory: ~/memory/sync/ βββ preferences.md # Synced from built-in βββ decisions.md # Synced from built-in Sync is one-way: Built-in β this system. Never modify built-in.
When a category grows large: INDEX.md > 100 entries β split into subcategories Create sub-INDEX.md for each subcategory Root INDEX.md points to subcategories ~/memory/projects/ βββ INDEX.md # "See active/, archived/" βββ active/ β βββ INDEX.md # 30 active projects β βββ ... βββ archived/ βββ INDEX.md # 200 archived projects βββ ...
Store HERE (~/memory/)Keep in BUILT-INDetailed project historiesCurrent project statusFull contact profilesKey contacts quick-refAll decision reasoningRecent decisionsDomain knowledge basesQuick factsCollections, inventoriesβAnything that grows largeSummaries Rule: Built-in for quick context. Here for depth and scale.
# Grep is fast enough grep -r "keyword" ~/memory/
Navigate via indices: 1. ~/memory/INDEX.md β find category 2. ~/memory/{category}/INDEX.md β find item 3. ~/memory/{category}/{item}.md β read details
Use semantic search if available, or hierarchical indices: ~/memory/projects/INDEX.md β "web projects in web/" ~/memory/projects/web/INDEX.md β "alpha project" ~/memory/projects/web/alpha.md β details
Update INDEX.md files if entries added Archive completed/inactive items
Review category sizes Split large categories Remove outdated entries
Check INDEX.md sizes (keep <100 lines) Split big categories into subcategories Archive old content
Modifying built-in memory β Never touch agent's MEMORY.md or workspace memory/. This system is parallel. No indices β Without INDEX.md, finding things requires searching all files. Always maintain indices. One giant category β 500 items in one folder is slow. Split into subcategories. Syncing everything β Don't copy all built-in memory. Only sync what needs organization here. Waiting to write β Write immediately when user shares info. Don't batch.
Data location: All data in ~/memory/ on user's machine No external services required No network requests This skill does NOT: Access built-in agent memory (only reads if syncing) Send data anywhere Store credentials (never store secrets in memory)
Install with clawhub install <slug> if user confirms: decide - Decision tracking patterns escalate - When to involve humans learn - Adaptive learning
If useful: clawhub star memory Stay updated: clawhub sync
Agent frameworks, memory systems, reasoning layers, and model-native orchestration.
Largest current source with strong distribution and engagement signals.