How do I install the Consolidate Memory skill?

Run npx skillmds@latest add furkangonel/consolidate-memory in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Consolidate Memory safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Consolidate Memory?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Consolidate Memory free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Consolidate Memory?

furkangonel (@furkangonel) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Consolidate Memory by furkangonel — Agent Skill

Name: Consolidate Memory
Author: furkangonel

Consolidate Memory

Reflective pass over your memory files — merge duplicates, fix stale facts, prune the index. Trigger for: - [TODO: Add specific triggers for when to use this skill] Don't trigger for: - [TODO: Add anti-triggers for when NOT to use this skill]

furkangonel 47ad3f2 2.4 KB Updated Sep 17, 2026

File contents

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. One line per entry, under ~150 chars: - [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.

Why/Failure Modes

[TODO: Explain the reasoning behind this skill's approach and common failure modes to avoid.]

Standalone vs Supercharged

[TODO: Describe how this skill works on its own vs when combined with other tools/context.]

Cross-References

[TODO: Link to other relevant skills or documentation.]

---name: consolidate-memorydescription: Reflective pass over your memory files — merge duplicates, fix stale facts, prune the index. Trigger for: - [TODO: Add specific triggers for when to use this skill] Don't trigger for: - [TODO: Add anti-triggers for when NOT to use this skill]---# Memory ConsolidationYou'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 indexUpdate `MEMORY.md` so it stays under 200 lines and ~25KB. One line per entry, under ~150 chars: `- [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 importantFinish with a short summary: how many files you touched and what changed.## Why/Failure Modes[TODO: Explain the reasoning behind this skill's approach and common failure modes to avoid.]## Standalone vs Supercharged[TODO: Describe how this skill works on its own vs when combined with other tools/context.]## Cross-References[TODO: Link to other relevant skills or documentation.]

Frequently asked questions