AgentStack
Sign in Publish
MCP servers Skills Toolkits Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Memory Cleanup

skill-ladyiceberg-openclaw-memory-quality-memory-cleanup · by ladyiceberg

Guided two-step cleanup for OpenClaw long-term memory (MEMORY.md) — audit first, confirm with user, then clean. Handles report_id automatically so the user never sees it. Use this skill whenever the user wants to clean, purge, or tidy their OpenClaw memories, mentions stale or old memories, or uses phrases like "clean memory", "cleanup memory", "delete old memories", "remove stale memories", "清理记…

↗ Repository
— No reviews yet
0 installs
3 views
0.0% view→install

Install

$ agentstack add skill-ladyiceberg-openclaw-memory-quality-memory-cleanup

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Memory Cleanup? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Memory Cleanup

Two-step guided cleanup. The user must confirm before anything is deleted. Never skip the confirmation step.

Step 1 — Audit

Call memory_longterm_audit_oc and store the returned report_id internally (never show it to the user).

Translate the results into plain language, e.g.:

> Found 23 long-term memories to handle: > - 8 with deleted source files (suggested for removal) > - 3 exact duplicates (suggested for removal) > - 12 flagged for review > > Estimated reduction: ~17% of MEMORY.md

If the audit shows everything is healthy, tell the user — no cleanup needed.

Step 2 — Confirm

Ask clearly: "Proceed with cleanup?"

  • Yes → Step 3
  • No / cancel → stop, do nothing
  • "Show details" → display the raw audit report, then ask again

Step 3 — Execute

Call memory_longterm_cleanup_oc with the report_id from Step 1. Report what was deleted, what was kept, and where the backup lives.

Error handling

| Error | Plain-language explanation | |-------|---------------------------| | MEMORY.md not found | "Long-term memory file doesn't exist yet — Dreaming may not have run." | | mtime changed | "MEMORY.md was modified after the audit (OpenClaw may have just promoted new memories). Please re-run /memory-cleanup." | | Lock timeout | "OpenClaw is currently writing to memory. Wait a moment and try again." |

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Agent Skills