mcpField
M
memory-manage

memory-manage

github.com/fearovex-labsAgent workflows51 installs
Repository

About memory-manage

memory-manage is a skill for managing the ai-context/ memory layer through initialization, updates, and maintenance. Its Claude Code execution notes also describe review and pinning operations with Engram.

Key features

  1. 01Three modes: init, update, maintain
  2. 02Engram observation decay review
  3. 03Pin canonical architecture and decision topics
  4. 04Unpin superseded topic heads

Use cases

  1. 01Initialize project memory files
  2. 02Update the ai-context/ memory layer
  3. 03Review observations due for decay checks
  4. 04Maintain canonical Engram topics

MCP support

The skill's Claude Code execution notes use Engram MCP operations including mem_review, mem_update, mem_pin, and mem_unpin.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/fearovex-labs/agent-config --skill memory-manage

After installing, type/memory-managein Claude Code to confirm it loaded.

Details

From the project README

memory-manage

Unified management of the ai-context/ memory layer. Three modes: init, update, maintain.

Triggers: /memory-init, /memory-update, /memory-maintain, initialize memory, update memory, maintain memory, memory housekeeping, clean ai-context

Claude execution wiring

These notes bind the tool-neutral logic above to the Claude Code harness. They are the EXECUTION layer that does not port to other tools.

  • Project instruction file — in the Claude harness the neutral "project instruction file" (maintain mode, gap detection) is CLAUDE.md at the project root.
  • Feature file format — the neutral "feature-domain-expert reference skill" resolves to ~/.claude/skills/feature-domain-expert/SKILL.md.
  • Decay review (mem_review) — maintain mode only, manual, no hook: call mem_review(action: "list") to fetch observations past their review_after; for each still-valid row call mem_review(action: "mark_reviewed", observation_id: <id>) to reset decay; stale rows get mem_update or are left to decay.
  • Pinning (mem_pin) — maintain mode pins ONLY canonical topic-key heads of types architecture/decision (policy: _shared/engram-convention.md, "Pinning Policy"). Pins are DEVICE-LOCAL, not synced — never claim a cross-device guarantee. mem_unpin superseded heads.

Comments

Markdown supported