manage-memory

Manage memory entries across workflow and system stores.

511|63|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/catlog22/Maestro-Flow --skill manage-memory-catlog22
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: manage-memory
Source: https://github.com/catlog22/Maestro-Flow/tree/main/.codex/skills/manage-memory
Command: npx skills add https://github.com/catlog22/Maestro-Flow --skill manage-memory-catlog22

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Memory management across workflow and system stores to keep memory entries organized, searchable, and up-to-date.

Core Features & Use Cases

  • List entries across both stores
  • Search, view, edit, delete, and prune memory records
  • Ensure index integrity and safe handling of destructive actions

Quick Start

Run manage-memory with a subcommand to view or modify memory entries.

Frequently Asked Questions about manage-memory

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

FAQPage Schema
How do I manage memory entries across different workflow stores?

You can manage memory entries across stores by using subcommands to list, search, view, edit, delete, and prune records. This handles both project workflow and local memory stores while maintaining index synchronization and safe destructive actions.

What is the best way to search and view memory records for project workflows?

Searching and viewing memory records for project workflows is done via specific subcommands that map and synchronize indexes. This ensures you retrieve accurate entries across both workflow and local system stores.

Can I edit and delete memory records without breaking index integrity?

Yes, you can edit and delete memory records safely because the system includes safety checks for destructive actions and index synchronization. This ensures memory management maintains index integrity across workflow and local stores.

How do I prune outdated memory entries from local memory stores?

You prune outdated memory entries from local memory stores using the prune subcommand. This safely removes records by applying safety checks for destructive actions and synchronizing indexes to keep remaining entries valid.

Why does memory management need index synchronization across stores?

Index synchronization is needed in memory management to keep entries searchable and accurate across stores. Without it, listing, searching, and viewing records would return outdated data between project workflows and local memory stores.