Recap
Roll up recent agent sessions and high-importance observations for the current project when you need continuity after a break.
Overview
recap is a journey-wide agent skill that summarizes recent AgentMemory sessions for the current project—usable whenever a solo builder needs to reload context on past agent work before committing to the next task.
Install
npx skills add https://github.com/rohitg00/agentmemory --skill recapWhat is this skill?
- Parses args: today, this week, last N, or default last 10 sessions
- Filters memory_sessions by current project cwd; groups output by local calendar date
- Pulls up to 3 highlight observations per session (importance ≥ 7) via memory_recall
- MCP-first with HTTP fallback to AGENTMEMORY_URL and optional bearer secret
- Default window: last 10 sessions when arguments are empty
- Up to 3 highlight observations per session at importance ≥ 7
Adoption & trust: 1.2k installs on skills.sh; 21.8k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You run many agent sessions on one repo and lose track of what was decided, tried, or left incomplete.
Who is it for?
Builders using AgentMemory MCP or HTTP API who want `/recap`, “this week”, or “last 5” style rollups tied to the active cwd.
Skip if: Projects without AgentMemory configured—there is no substitute data source beyond documented MCP/HTTP endpoints.
When should I use this skill?
User asks recap, what have we been doing, this week, today, or wants a rollup of recent work; argument-hint supports last N | today | this week.
What do I get? / Deliverables
You get a date-grouped recap with session summaries, top observations per session, and a one-line total count—or a clear empty-window message without invented sessions.
- Date-grouped session recap with observation highlights
- One-line totals: sessions, days, observation count
Recommended Skills
Journey fit
Useful at every journey phase - explore requirements and options before committing to a direction.
Where it fits
Monday morning recap of last week’s sessions before picking up an in-flight bugfix branch.
New agent thread runs recap to see which features were already attempted and which observations flagged blockers.
Before expanding MVP scope, recap confirms what prototyping work already happened this week.
Pre-release recap surfaces sessions where testing or review topics were recorded as high-importance observations.
How it compares
Session rollup over AgentMemory—not a generic chat exporter or long-term knowledge base authoring skill.
Common Questions / FAQ
Who is recap for?
Solo developers and agent-heavy workflows on a single codebase who store session history in AgentMemory and need quick situational awareness.
When should I use recap?
Use at Operate when resuming after days away, at Build when spinning a new agent with prior context, or anytime you ask recap, what have we been doing, today, or this week.
Is recap safe to install?
Review the Security Audits panel on this page; recap reads project-scoped session data via MCP/HTTP and should use least-privilege AGENTMEMORY_SECRET.
SKILL.md
READMESKILL.md - Recap
The user wants a recap. Time window args: $ARGUMENTS Parse `$ARGUMENTS` to determine the window: - `today` -> sessions started on the current local date - `this week` -> sessions started in the last 7 days - `last <n>` -> the most recent N sessions - bare numeric -> treat as `last <n>` - empty -> default to `last 10` Call the `memory_sessions` MCP tool, then filter to the current project (match by `cwd` against the working directory). Apply the time window. Sort by `startedAt` descending. Group the surviving sessions by their local calendar date (YYYY-MM-DD). For each date: - List each session: id (first 8 chars), title or first prompt, observation count, status - Indent two or three highlight observations per session (importance >= 7) drawn from `memory_recall` with a per-session query, limit 3 End with a one-line total: "N sessions across M days, K observations." If MCP tools are unavailable, fall back to HTTP: `GET $AGENTMEMORY_URL/agentmemory/sessions` and `POST $AGENTMEMORY_URL/agentmemory/recall` with `Authorization: Bearer $AGENTMEMORY_SECRET` when set. Do not invent sessions; if the window is empty, say so.