Consolidate Memory
Reflective pass over your memory files — merge duplicates, fix stale facts, prune the index.
Install
$ agentstack add skill-organvm-a-i-skills-consolidate-memory ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo 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.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-organvm-a-i-skills-consolidate-memory) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Memory Consolidation
You're doing a reflective pass over what you've learned about this user and their work. The goal: a future session should be able to orient quickly — who they work with, what they're focused on, how they like things done — without re-asking.
Your system prompt's auto-memory section defines the directory, file format, and memory types. Follow it.
Phase 1 — Take stock
- List the memory directory and read the index (
MEMORY.md) - Skim each topic file. Note which ones overlap, which look stale, which are thin.
Phase 2 — Consolidate
Separate the durable from the dated. Preferences, working style, key relationships, and recurring workflows are durable — keep and sharpen them. Specific projects, deadlines, and one-off tasks are dated — if the date has passed or the work is done, retire the file or fold the lasting takeaway (e.g. "user prefers X format for launch docs") into a durable one.
Merge overlaps. If two files describe the same person, project, or preference, combine into one and keep the richer file's path.
Fix time references. Convert "next week", "this quarter", "by Friday" to absolute dates so they stay readable later.
Drop what's easy to re-find. If a memory just restates something you could pull from the user's calendar, docs, or connected tools on demand, cut it. Keep what's hard to re-derive: stated preferences, context behind a decision, who to go to for what.
Phase 3 — Tidy the index
Update MEMORY.md so it stays under 200 lines and ~25KB. Each entry is one line, under ~150 chars, in this format:
- [Title](file.md) — one-line hook- Remove pointers to retired memories
- Shorten any line carrying detail that belongs in the topic file
- Add anything newly important
Finish with a short summary: how many files you touched and what changed.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: organvm
- Source: organvm/a-i--skills
- License: Apache-2.0
- Homepage: https://organvm.github.io/a-i--skills/
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.