← All skills
Tencent SkillHub Β· AI

OpenClaw Memory

Session-first memory curator for OpenClaw. Keeps RAM clean, recall precise, and durable knowledge safe.

skill openclawclawhub Free
0 Downloads
0 Stars
0 Installs
0 Score
High Signal

Session-first memory curator for OpenClaw. Keeps RAM clean, recall precise, and durable knowledge safe.

⬇ 0 downloads β˜… 0 stars Unverified but indexed

Install for OpenClaw

Quick setup
  1. Download the package from Yavira.
  2. Extract the archive and review SKILL.md first.
  3. Import or place the package into your OpenClaw setup.

Requirements

Target platform
OpenClaw
Install method
Manual import
Extraction
Extract archive
Prerequisites
OpenClaw
Primary doc
SKILL.md

Package facts

Download mode
Yavira redirect
Package format
ZIP package
Source platform
Tencent SkillHub
What's included
SKILL.md

Validation

  • Use the Yavira download entry.
  • Review SKILL.md after the package is downloaded.
  • Confirm the extracted package contains the expected setup assets.

Install with your agent

Agent handoff

Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.

  1. Download the package from Yavira.
  2. Extract it into a folder your agent can access.
  3. Paste one of the prompts below and point your agent at the extracted folder.
New install

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.

Upgrade existing

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.

Trust & source

Release facts

Source
Tencent SkillHub
Verification
Indexed source record
Version
2.1.0

Documentation

ClawHub primary doc Primary doc: SKILL.md 20 sections Open source page

OpenClaw Memory Curator

A session-first memory system for OpenClaw. It exists for one reason: important knowledge must survive session compaction without bloating the context window.

TL;DR (for humans)

Session memory = temporary (RAM) Disk = source of truth Decisions & preferences β†’ MEMORY.md Daily work β†’ memory/YYYY-MM-DD.md This skill saves durable knowledge before compaction Retrieval always happens via memory_search β†’ memory_get If something matters later, write it to disk. ⚠️ CRITICAL REQUIREMENT Session memory indexing must be enabled.

Enable Session Memory

CLI clawdbot config set agents.defaults.memorySearch.experimental.sessionMemory true JSON { "agents": { "defaults": { "memorySearch": { "experimental": { "sessionMemory": true }, "sources": ["memory", "sessions"] } } } }

Mental Model (read this once)

OpenClaw memory has three layers. Confusion usually comes from mixing them up.

1. Session Memory (RAM)

Lives in the current conversation Automatically compacted Indexed for retrieval Never reliable long-term πŸ‘‰ Treat as short-term thinking space.

2. Daily Logs (memory/YYYY-MM-DD.md)

Append-only What happened today Commands, edits, short-lived issues πŸ‘‰ Treat as a work log, not a knowledge base.

3. Long-Term Memory (MEMORY.md)

Curated Small High-signal only Indexed and retrievable πŸ‘‰ Treat as facts the agent must not forget.

Write to MEMORY.md if it would still be true next week.

Examples: Decisions Preferences Invariants Policies

Write to daily logs if it helps understand today.

Examples: Refactors Experiments Temporary blockers If unsure: write to daily log first, promote later.

Pre-Compaction Flush (why this exists)

Before OpenClaw compacts the session, it triggers a silent reminder. This skill uses that moment as a Save Game checkpoint.

What happens:

Durable knowledge is extracted Daily notes are written to today’s log Durable items are promoted to MEMORY.md Agent replies NO_REPLY (user never sees this) This prevents knowledge loss without interrupting you.

Durable Memory Format (MEMORY.md)

Use IDs and tags so search works reliably. ## DEC-2026-02-04-01 type: decision area: memory Decision: Session memory is retrieval-only. Disk is the source of truth. Reason: Session compaction is lossy. Disk memory is stable.

ID prefixes

DEC – Decisions PREF – Preferences FACT – Durable facts POLICY – Rules / invariants

Retrieval Strategy (how agents should recall)

Use memory_search (max ~6 results) Pick the best 1–2 hits Use memory_get with line ranges Inject the minimum text required This keeps context small and precise.

Agent Playbook (rules for agents)

Prefer disk over RAM Prefer MEMORY.md over daily logs for facts Use search before asking the user again Never copy raw chat into memory Write memory explicitly, do not assume it sticks

Anti-Patterns (do not do these)

❌ Copy chat transcripts into memory ❌ Store secrets or credentials ❌ Treat daily logs as long-term memory ❌ Overwrite memory files instead of appending ❌ Store speculation as fact

Privacy Rules

Never store secrets (API keys, tokens, passwords) Ignore anything inside <private>...</private> If sensitive info exists: store only that it exists, not the value

Retention & Cleanup

Default: no deletion Disk is cheap Recall quality is expensive Optional: Move old daily logs to memory/archive/YYYY-MM/ Only prune after durable knowledge is verified

Usage (human-friendly)

Examples that work well: β€œStore this as a durable decision.” β€œThis is a preference, remember it.” β€œWrite this to today’s log.”

Design Philosophy

Disk is truth RAM is convenience Retrieval beats retention Fewer tokens > more tokens Memory should earn its place

Category context

Agent frameworks, memory systems, reasoning layers, and model-native orchestration.

Source: Tencent SkillHub

Largest current source with strong distribution and engagement signals.

Package contents

Included in package
1 Docs
  • SKILL.md Primary doc