OpenSkillIndex← back to search
claude-codeopenclaw

Openclaw-superpowers persistent-memory-hygiene

Keeps OpenClaw's memory store clean, structured, and useful. Use at session end and during periodic maintenance.

install
source · Clone the upstream repo
git clone https://github.com/ArchieIndian/openclaw-superpowers
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/ArchieIndian/openclaw-superpowers "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/openclaw-native/persistent-memory-hygiene" ~/.claude/skills/archieindian-openclaw-superpowers-persistent-memory-hygiene && rm -rf "$T"
OpenClaw · Install into ~/.openclaw/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/ArchieIndian/openclaw-superpowers "$T" && mkdir -p ~/.openclaw/skills && cp -r "$T/skills/openclaw-native/persistent-memory-hygiene" ~/.openclaw/skills/archieindian-openclaw-superpowers-persistent-memory-hygiene && rm -rf "$T"
manifest: skills/openclaw-native/persistent-memory-hygiene/SKILL.md
source content

Persistent Memory Hygiene

State file: 

~/.openclaw/skill-state/persistent-memory-hygiene/state.yaml

Memory Structure

memory/
  YYYY-MM-DD.md    # Daily notes - raw, comprehensive
MEMORY.md          # Long-term - curated, distilled

When to Write

Write to memory/YYYY-MM-DD.md when:

  • Completing a significant task
  • Making a decision with reasoning
  • Encountering a notable error and its fix
  • At checkpoints on long tasks

Write to MEMORY.md when:

  • Something is worth remembering across months
  • A user preference has been established
  • A pattern has been confirmed

Session Closing Routine

## [HH:MM] Session End
- Completed: [what was finished]
- In progress: [what was started]
- Next: [what to do next session]
- Decisions: [choices made and why]

After writing, update state: 

last_cleaned_at
, 
memory_line_count
, 
daily_file_count
, 
last_daily_file
, 
status: done
.

Hygiene Rules

  • Daily files: write raw, append-only, never edit old entries
  • MEMORY.md: review periodically, remove stale entries, keep under 500 lines

Cron Wakeup Behavior

On 11pm wakeup:

  • Read state file
  • If 
    last_cleaned_at
    is today's date: skip (already ran)
  • Otherwise: run Session Closing Routine, update state