consolidate-memory

Scan MEMORY.md files to tag bullets older than 30 days as stale.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/BinatrixAI/tandem-marketplace --skill consolidate-memory-binatrixai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: consolidate-memory
Source: https://github.com/BinatrixAI/tandem-marketplace/tree/main/plugins/tandem/skills/core/consolidate-memory
Command: npx skills add https://github.com/BinatrixAI/tandem-marketplace --skill consolidate-memory-binatrixai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates memory freshness by scanning all central and local MEMORY.md files, tagging entries older than 30 days as stale, and demoting them from the compiled truth while preserving the timeline evidence.

Core Features & Use Cases

  • Scans central and local memory files to identify aged memory bullets
  • Marks aged bullets as stale by rewriting their inline metadata without changing the text
  • Removes corresponding compiled-truth bullets from the truth view while keeping the timeline intact
  • Skips legacy or pre-retrofit files and reports them for lazy retrofit in memory-create workflows

Quick Start

Run a staleness pass across all MEMORY.md files to mark outdated entries as stale.

Frequently Asked Questions about consolidate-memory

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate memory freshness by tagging outdated memory bullets as stale?

To automate memory freshness, you scan central and local MEMORY.md files to identify memory bullets older than 30 days and tag them as stale by rewriting their inline metadata tier without altering the original bullet text.

What happens to compiled-truth bullets when memory entries are marked as stale?

When memory entries are marked as stale, the corresponding compiled-truth bullets are removed from the timeline's truth view while the original timeline evidence and bullet text are preserved intact.

How does stale-tagging handle legacy or pre-retrofit MEMORY.md files?

Stale-tagging skips legacy or pre-retrofit MEMORY.md files entirely during the scanning process and reports them separately for lazy retrofit in memory-create workflows.

Can I change the 30-day threshold for identifying stale memory bullets?

The metadata does not mention changing the 30-day threshold. The staleness pass identifies memory bullets older than 30 days by default to tag them as stale and remove them from the compiled truth.

Does stale-tagging alter the original text of memory bullets in MEMORY.md files?

Stale-tagging does not alter the original memory bullet text. It only rewrites the inline metadata tier to mark the entry as stale while preserving the bullet content in the timeline.

What reporting is provided after a memory consolidation staleness pass?

After a staleness pass, the process reports a final tally of tagged entries, demoted compiled-truth bullets, and legacy-skipped files for tracking memory consolidation accuracy.