openclaw-memorybox_skill

This skill helps you maintain lean MEMORY.md and automate three-tier memory organization for OpenClaw, reducing context drift and storage bloat.
  • Python

2.5k

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill openclaw-memorybox

  • _meta.json281 B
  • SKILL.md2.1 KB

Overview

This skill is a zero-dependency CLI that keeps OpenClaw agent memory lean by enforcing a simple, three-tier hierarchical structure. It automates diagnostics, archiving, and redistribution of memory content so MEMORY.md stays small and relevant. Install once and use its commands to monitor, split, archive, and report on memory usage without touching configs or plugins.

How this skill works

MemoryBox inspects the agent's memory files and reorganizes content into three tiers: a compact MEMORY.md for core facts, domain files for detailed reference, and an archive for old logs. It provides commands to diagnose bloat, split oversized sections into domain files, archive aged logs, deduplicate content, and generate health and savings reports. All operations are file-structure only, leaving runtime configs and plugins unchanged.

When to use it

  • When MEMORY.md grows beyond the recommended size or causes context pressure.
  • Before deploying an agent to reduce token usage and improve response quality.
  • To archive old daily logs and reduce clutter without losing historical data.
  • When integrating or coexisting with other memory tools like Mem0, Supermemory, or QMD.
  • During routine maintenance to detect stale or duplicated memory entries.

Best practices

  • Keep MEMORY.md under 10KB and store detailed notes in memory/domains/*.md.
  • Run memorybox doctor after major updates or periodic cron changes.
  • Use memorybox split interactively to move only necessary sections to domain files.
  • Archive logs older than two weeks to memory/archive to preserve history without context cost.
  • Check memorybox report after changes to confirm token savings and reduced context pressure.

Example use cases

  • Shrink a bloated MEMORY.md from tens of KB to a few KB before scaling the agent.
  • Automatically archive daily chat logs older than 14 days to free up working memory.
  • Detect and remove duplicate passages introduced by repeated cron outputs.
  • Generate a health score and improvement suggestions to track memory hygiene over time.
  • Initialize the three-tier directory structure for a new OpenClaw agent in minutes.

FAQ

No. MemoryBox only modifies the file structure and content in memory directories; it does not touch runtime configs or plugins.

Can MemoryBox work alongside other memory systems?

Yes. It is designed to coexist with Mem0, Supermemory, QMD, or run standalone without conflicts.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational