Memory Keeper
Scanned@CrimsonDevil333333
npx machina-cli add skill @CrimsonDevil333333/memory-keeper --openclawMemory Keeper
Memory Keeper is a simple CLI that copies the critical OpenClaw context files (daily memory logs, DESCRIPTION.md, personality documents, heartbeat reminders) into a safe archive destination and optionally commits/pushes them to a configured git repo. It keeps the same file layout so you can restore or inspect the history without grabbing the whole workspace.
Features
- Snapshots: Copies
memory/*.md,MEMORY.md,AGENTS.md,SOUL.md,USER.md,TOOLS.md,HEARTBEAT.md, and optional extras into the archive path while preserving directory structure. - Git-friendly: If the target archive is a git repo, Memory Keeper can initialize it, create commits, and push changes to your remote branch (configurable via CLI flags).
- Portable: Works on any platform; just point
--workspaceto a workspace root containing those files.
Get started
python3 skills/memory-keeper/scripts/memory_sync.py --target ~/clawdy-memories --commit --message "Sync up" --remote https://github.com/your-org/clawdy-memories.git --push
See references/usage.md for configuration tips, automation recipes, and a troubleshooting guide.
Resources
Overview
Memory Keeper is a simple CLI that snapshots critical agent context files (MEMORY.md, memory/*.md, AGENTS.md, SOUL.md, HEARTBEAT.md, and related docs) into a dedicated archive path. It preserves the original directory layout to ease restoration and can optionally commit and push changes to a configured git repo for maintenance, corruption recovery, or transferring to another host.
How This Skill Works
Point Memory Keeper at your workspace and specify a target archive. It copies the labeled context files while preserving directory structure. If the destination is a git repository, it can initialize the repo, create commits, and push updates to the configured remote.
When to Use It
- Before maintenance or upgrades to protect context
- When migrating context to a new host or workspace
- After updates to MEMORY.md, SOUL.md, or personality documents to capture a snapshot
- For audits, backups, and compliance documentation
- To support disaster recovery by preserving a restore point
Quick Start
- Step 1: Run memory_sync.py with --workspace and --target to copy context files to the archive
- Step 2: If versioning is desired, add --commit --message 'Backup' and optionally --remote and --push to update a git repo
- Step 3: Verify the archive by listing the directory and, if using git, checking the latest commit
Best Practices
- Back up all relevant files: MEMORY.md, memory/*.md, AGENTS.md, SOUL.md, USER.md, TOOLS.md, HEARTBEAT.md, and any extras
- Preserve the original directory structure in the archive for easy restoration
- Use a descriptive commit message when enabling git push (e.g., 'Backup before upgrade')
- Verify archive integrity by listing files and spot-checking contents
- Schedule regular backups during low-activity windows and document the archive path
Example Use Cases
- Backing up daily memories and heartbeat reminders before a major system update
- Migrating agent context to a new host using the archive as the source of truth
- Creating a baseline archive after updating personality documents and rules
- Archiving prior to a data purge to ensure a restorable state
- Storing a compliance copy of AGENTS.md and SOUL.md for audits
