AgentStack
SKILL verified MIT Self-run

Agent Prompt: Dream memory pruning

skill-lord1egypt-ai-skillforge-agent-prompt-dream-memory-pruning · by Lord1Egypt

Instructs an agent to perform a memory pruning pass by deleting stale or invalidated memory files and collapsing duplicates in the memory directory

No reviews yet
0 installs
11 views
0.0% view→install

Install

$ agentstack add skill-lord1egypt-ai-skillforge-agent-prompt-dream-memory-pruning

✓ 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 Agent Prompt: Dream memory pruning? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Dream: Memory Pruning

You are performing a dream — a pruning pass over your memory files. The job is small: delete stale or invalidated memories, and collapse duplicates.

Memory directory: ${MEMORY_DIR} ${MEMORYDIRCONTEXT}

Memory files are immutable: never edit them in place. Combining means deleting the old files and (if needed) writing one fresh single-fact file in their place.

What to do

  1. find ${MEMORY_DIR} -name '*.md' to enumerate every memory file (including any team/ subdirectory).
  2. For each memory file, decide:
  • Stale or invalidated — the fact no longer holds (contradicted by current code, the project moved on, the user's preference changed). Delete the file.
  • Duplicate or near-duplicate — another memory already covers the same fact. Delete the redundant copies. If a single richer single-fact memory would replace the cluster, delete the cluster and write one fresh file (use the format and type conventions from your system prompt's auto-memory section). When you write the combined replacement, copy the created: date from the oldest source memory's frontmatter so manifest sort order stays accurate.
  • Still good — leave it alone.${HASTEAMMEMORY_NOTE?"\n\nteam/ subdirectory — these memories are shared across teammates; other people's sessions write here. Be conservative: only delete a team/ file when it's clearly contradicted or a newer team memory marks it as superseded. Do NOT delete a team memory just because you don't recognize it or it isn't relevant to your recent sessions — a teammate may rely on it. Do not move personal memories into team/.":""}

Return a brief summary of what you deleted, combined, or left alone. If nothing changed, say so.${ADDITIONAL_CONTEXT?`

Additional context

${ADDITIONAL_CONTEXT}`:""}

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.

Versions

  • v0.1.0 Imported from the upstream source.