memory-maintenance

Étoiles10

Forks1

Mis à jour11 juillet 2026 à 05:20

Inspect, consolidate, audit, forget, or restore Aionforge Memory. Use when the user asks about memory health, backlog, provenance, stale records, corrections, deletion, restoration, or why a memory was recalled.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Source

jscott3201

jscott3201/aionforge-memory

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Métiers associésSOC

Basé sur la classification professionnelle SOC

Autres occupations informatiquesProfessions informatiques et mathématiques·SOC 15-1299

Explorateur de fichiers

2 fichiers

SKILL.md

readonly

name	memory-maintenance
description	Inspect, consolidate, audit, forget, or restore Aionforge Memory. Use when the user asks about memory health, backlog, provenance, stale records, corrections, deletion, restoration, or why a memory was recalled.
license	MIT OR Apache-2.0
metadata	{"aionforge-version":"0.4.1"}

Memory Maintenance

Requires an enabled Aionforge Memory MCP server.

Use this skill when the task is about the memory system itself.

Procedure

Call server_status if connection state is unknown.
Call consolidation_status to inspect backlog or failed derived work.
Run consolidate only when the user/project policy permits mutating derived memory.
Use audit_history to explain provenance, capture receipts, supersession hints, lifecycle changes, and rejection reasons.
Use forget or unforget only when the user explicitly names the target memory id or asks for a specific lifecycle change.
After lifecycle changes, search again when the user needs confirmation of visible recall state.

Scope

This skill maintains memory episodes and their derived work: consolidation, audit, decay, forget, and restore.
Work items are out of scope here. They are persistent and exempt from decay and forget; manage them with the work-tracking skill (work_advance to retire one to done/dropped), not forget. work_advance is itself audited, so audit_history still explains a work item's transitions.

Defaults

Preserve memory ids in answers.
Prefer audit evidence over guesses.
Treat ERR_NOT_FOUND as absent or unauthorized; do not infer hidden memory existence.

Plus depuis ce dépôt

même dépôt

agent-messaging

jscott3201/aionforge-memory

Send, poll, wait for, and acknowledge durable addressed agent-to-agent messages in Aionforge Memory (message_send, message_poll, message_wait, message_ack) and subscribe to room resources. Use to hand a brief to another agent, page a teammate, wait for a reply, coordinate a multi-agent workflow, or drain an inbox — distinct from recall and work tracking.

2026-07-1110

memory-bootstrap

jscott3201/aionforge-memory

One-time setup that lays a foundational Aionforge Memory substrate for a fresh project — resolve identity, seed conventions and architecture decisions as captures, stand up a work-item backlog skeleton, and verify recall. Use when a project's memory is empty or new, or when the user asks to set up, bootstrap, initialize, or seed project memory.

2026-07-1110

memory-capture

jscott3201/aionforge-memory

Capture durable Aionforge Memory records for decisions, user preferences, project facts, release outcomes, validation results, handoffs, corrections, and reusable failure patterns. Use proactively during substantial work and whenever the user asks to remember or update memory.

2026-07-1110

memory-loop

jscott3201/aionforge-memory

Use Aionforge Memory as the working substrate for a multi-step task. Trigger for implementation, debugging, review, release, planning, incidents, handoffs, or any session where prior context and durable follow-up matter.

2026-07-1110

memory-recall

jscott3201/aionforge-memory

Search Aionforge Memory before planning, answering, coding, review, debugging, release, or continuation work. Use proactively whenever prior decisions, user preferences, project facts, failures, or handoffs could change the answer.

2026-07-1110

work-tracking

jscott3201/aionforge-memory

Track tasks, blockers, TODOs, plans, and follow-ups as durable Aionforge Memory work items. Use proactively when a multi-step task, backlog, plan, or handoff appears, and whenever the user mentions tasks, status, or what is left to do. Work items are persistent and status-tracked, distinct from decaying memory episodes.

2026-07-1110

name	memory-maintenance
description	Inspect, consolidate, audit, forget, or restore Aionforge Memory. Use when the user asks about memory health, backlog, provenance, stale records, corrections, deletion, restoration, or why a memory was recalled.
license	MIT OR Apache-2.0
metadata	{"aionforge-version":"0.4.1"}

Memory Maintenance

Requires an enabled Aionforge Memory MCP server.

Use this skill when the task is about the memory system itself.

Procedure

Call server_status if connection state is unknown.
Call consolidation_status to inspect backlog or failed derived work.
Run consolidate only when the user/project policy permits mutating derived memory.
Use audit_history to explain provenance, capture receipts, supersession hints, lifecycle changes, and rejection reasons.
Use forget or unforget only when the user explicitly names the target memory id or asks for a specific lifecycle change.
After lifecycle changes, search again when the user needs confirmation of visible recall state.

Scope

This skill maintains memory episodes and their derived work: consolidation, audit, decay, forget, and restore.
Work items are out of scope here. They are persistent and exempt from decay and forget; manage them with the work-tracking skill (work_advance to retire one to done/dropped), not forget. work_advance is itself audited, so audit_history still explains a work item's transitions.

Defaults

Preserve memory ids in answers.
Prefer audit evidence over guesses.
Treat ERR_NOT_FOUND as absent or unauthorized; do not infer hidden memory existence.