菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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.
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.
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.
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.
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.
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.
| name | memory-capture |
| description | 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. |
| license | MIT OR Apache-2.0 |
| metadata | {"aionforge-version":"0.4.1"} |
Requires an enabled Aionforge Memory MCP server.
Use this skill to make useful work durable. Prefer several focused captures over one sparse summary.
Capture as you go, not at the end. The moment a durable fact lands — a decision made, a fix verified, a release or CI state change, a user preference learned, an approach rejected — write it. Batching to the end loses the precise context, and a context compaction can discard it first.
capture writes a memory episode: a durable fact that decays over time and can be superseded or forgotten. Two things are not episodes:
work-tracking skill (work_create → work_advance); work items persist and are status-tracked.consolidate from episodes — never written by hand. If a "note" tempts you, it is either a durable fact (capture) or a thing to do (work_create).AIONFORGE_AGENT_ID; otherwise use the stable UUID supplied by the user or project instructions.role: assistant for session summaries and decisions; use role: event for external project events.supersedes.consolidation_status; run consolidate only when tool approval policy and user/project rules allow mutating derived memory.