journal-optimizer

Audit and prune low-value journal entries in memory-journal-mcp with backups.

19|6|Updated Sep 13, 2025
One-click install
npx skills add https://github.com/neverinfamous/memory-journal-mcp --skill journal-optimizer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: journal-optimizer
Source: https://github.com/neverinfamous/memory-journal-mcp/tree/main/skills/journal-optimizer
Command: npx skills add https://github.com/neverinfamous/memory-journal-mcp --skill journal-optimizer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams manage memory-journal-mcp databases by guiding safe pruning and maintenance of journal entries, reducing bloat and preserving recoverability.

Core Features & Use Cases

  • Guided workflows for pruning low-value entries using importance scores, relationship density, and entry metadata to identify candidates for soft-deletion while preserving recoverability via backups.
  • Safe deletion protocol with gating backups and revert guidance, and a central journal entry to audit maintenance.
  • Orphan and duplicate cleanup, type-based cleanup, and post-optimization maintenance like rebuilding vector indices.
  • Use cases include reducing storage footprint, improving query performance, and maintaining long-term AI context within journal workflows.

Quick Start

Begin with a dry-run audit to surface low-value entries and review the recommended candidates before performing any deletions.

Frequently Asked Questions about journal-optimizer

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

FAQPage Schema
How do I prune low-value entries in a memory journal database safely?

Database pruning for memory journals involves auditing importance scores, detecting orphan and duplicate entries, and executing type-based cleanup with mandatory backups to reduce storage bloat and improve query performance.

How do I clean up orphan and duplicate journal entries without losing data?

Yes, you can revert deleted journal entries if you enforce a backup using backup_journal before pruning, which captures the database state and provides explicit revert guidance for recovering soft-deleted data.

What is the best way to reduce memory journal storage bloat and improve query performance?

Run a dry-run audit to surface low-value entries and review recommended candidates before performing deletions, ensuring memory journal optimization only targets data with low importance scores and relationship density.

When should I avoid deleting entries from a memory journal?

You should avoid deleting memory journal entries when a backup has not been successfully created, as the workflow restricts destructive actions and enforces backup_journal to ensure traceability and recoverability.