菜单
Summarize the last N agent sessions for the current project, grouped by date, with highlight observations per session. Use when the user asks "recap", "what have we been doing", "today", "this week", or wants a rollup of recent work.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | recap |
| description | Summarize the last N agent sessions for the current project, grouped by date, with highlight observations per session. Use when the user asks "recap", "what have we been doing", "today", "this week", or wants a rollup of recent work. |
| argument-hint | [last N | today | this week] |
| user-invocable | true |
The user wants a recap. Time window args: $ARGUMENTS
memory_sessions { "limit": 30 }
Then per surviving session: memory_recall { "query": "<top concepts>", "limit": 3 }.
Expected output:
2026-06-07
7f3a9c2 · "Auth refresh rework" · 14 obs · completed
- [8] Rotate refresh tokens on every use
3 sessions across 2 days, 41 observations.
Only summarize sessions and observations the tools returned. An empty window is a real answer, not a prompt to invent activity.
$ARGUMENTS: today = current local date; this week = last 7 days;
last <n> or bare numeric = most recent N; empty = last 10.memory_sessions, filter to the current project (match cwd against the
working directory), apply the window, sort by startedAt descending.memory_recall.WRONG: window is empty, so you summarize "a productive week of auth work" from memory of the conversation.
RIGHT: "No sessions in the last 7 days for this project."
memory_recall, not paraphrase.handoff, session-history, recall: same session data, different lens.See ../_shared/TROUBLESHOOTING.md if memory_sessions or memory_recall is not available.
How agentmemory wires into host coding agents via the connect command. Use when installing agentmemory into a specific agent, when asked which agents are supported, or when a connect adapter writes the wrong config path.
How agentmemory is built, the iii engine primitives it runs on, its storage model, ports, and the viewer. Use when reasoning about how memory is stored or retrieved end to end, when extending the system, or when answering how agentmemory works under the hood.
agentmemory configuration, environment variables, ports, and feature flags. Use when enabling a feature, changing ports, setting an API key, configuring auth, or explaining why a feature is off by default.
The agentmemory plugin hooks that capture observations automatically across the agent session lifecycle. Use when explaining how memory gets captured without manual saves, when debugging missing observations, or when tuning what gets recorded.
Map of every agentmemory MCP tool, what each does, and its parameters. Use when choosing which memory tool to call, when a tool name or argument is unclear, or when answering what agentmemory can do via MCP.
The agentmemory HTTP REST API surface, the primary protocol for talking to the memory server. Use when calling agentmemory over HTTP, when MCP is unavailable and you need a fallback, or when integrating a host that does not speak MCP.