memory-management

Inspect and curate approved standing user preferences and constraints in scoped memory.

6|Updated Jun 25, 2026
One-click install
npx skills add https://github.com/tribgames/mixdog --skill memory-management-tribgames
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: memory-management
Source: https://github.com/tribgames/mixdog/tree/main/src/defaults/skills/memory-management
Command: npx skills add https://github.com/tribgames/mixdog --skill memory-management-tribgames

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Long-running AI workflows accumulate user preferences and constraints that should persist across sessions, but without curation they become cluttered with inferred lessons, task outcomes, and duplicated settings. This Skill governs how standing memory entries are reviewed, approved, scoped, and maintained so only deliberate user preferences persist. ## Core Features & Use Cases - Approval-gated curation: Shows the exact content and scope of any memory addition or edit and requires explicit user approval before writing. - Scoped memory management: Supports common memory, per-Project memory via project_id, and read-only wildcard scope, with per-scope indices starting at 1. - Safe edit and delete operations: Uses exact project_id, id, and index_revision values from listings, with stale-version recovery by re-reading the list instead of blind retries. - Use Case: A user asks to remember that they prefer concise commit messages. The Skill drafts the exact statement, confirms the target Project scope, obtains approval, and writes it to standing memory. ## Quick Start Ask the assistant to remember a specific preference, such as requesting that it store your preferred code review style in the current Project's memory.

Frequently Asked Questions about memory-management

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

FAQPage Schema
How do I save a user preference to persistent memory?▼

State the exact preference you want stored and its scope. The Skill shows the precise content and target scope for approval before writing, then stores it as a compact English statement via the memory tool.

What is the difference between memory and conversation history?▼

Memory holds only curated, user-approved standing preferences and constraints. Past sessions, decisions, and automatic summaries remain searchable history through recall and never become standing instructions automatically.

How do memory scopes and project_id work?▼

Omit project_id for the current Project, use common for shared memory, or pass an explicit Project slug for another Project. The wildcard scope is read-only, and indices start at 1 independently per scope.

Why did my memory edit fail with a stale version error?▼

Edits and deletes require the exact id and index_revision from the latest list. On a stale-version error, re-read the list, identify the intended entry again, and retry with fresh values instead of reusing old indices.

What should not be stored in standing memory?▼

Do not store inferred lessons, ordinary task outcomes, repository state, or duplicates of profile, settings, rules, or tool contracts. Automatic history already preserves task outcomes, so memory stays limited to deliberate preferences.