PluginBench
Skill
Fail
Audit score 45

recap

rohitg00/agentmemory

Summarize recent agent sessions grouped by date with key observations from project memory.

What is recap?

Recap retrieves and organizes the last N agent sessions for your current project, grouped by calendar date with highlighted observations per session. Use it when you need a rollup of recent work, progress on specific dates, or want to understand what's been accomplished over a time window (today, this week, or last N sessions).

  • Parse time window arguments (today, this week, last N, or default last 10 sessions)
  • Retrieve sessions filtered to the current project's working directory
  • Group sessions by local calendar date (YYYY-MM-DD)
  • Display session ID, title/first prompt, observation count, and status
  • Extract and indent 2-3 high-importance observations (≥7) per session
  • Report totals: N sessions across M days, K observations

How to install recap

npx skills add https://github.com/rohitg00/agentmemory --skill recap
Prerequisites
  • memory_sessions tool must be available
  • memory_recall tool must be available
  • Current project working directory must be set
Claude Code
Cursor
Windsurf
Cline

How to use recap

  1. 1.Invoke the skill with a time window argument: 'recap today', 'recap this week', 'recap last 5', or 'recap' (defaults to last 10)
  2. 2.The skill parses your argument and queries memory_sessions for matching sessions in your project
  3. 3.Sessions are grouped by date and sorted with most recent first
  4. 4.For each session, key observations (importance ≥7) are retrieved and displayed as indented highlights
  5. 5.Review the summary to understand recent progress, then ask follow-up questions about specific sessions if needed

Use cases

Good for
  • Ask 'what have we been doing this week?' to see project progress grouped by date
  • Request 'recap today' to review all work completed in the current session date
  • Use 'last 5' to focus on the most recent 5 sessions and their key findings
  • Check 'this week' to understand scope and highlights across multiple days of work
  • Verify session history before handing off to another agent or team member
Who it's for
  • Agents needing to summarize their own recent work
  • Users reviewing project progress over time
  • Teams coordinating handoffs between sessions or agents
  • Developers tracking what was accomplished across multiple coding sessions

recap FAQ

What happens if there are no sessions in the requested time window?

The skill returns 'No sessions in the last N days for this project.' It does not invent activity from conversation memory.

How are sessions filtered to my project?

Sessions are matched against your current working directory (cwd). Only sessions from the same project directory are included.

Where do the highlighted observations come from?

Highlights are retrieved via memory_recall with importance ≥7. They are not paraphrased; they come directly from stored observations.

What time window arguments are supported?

'today' (current local date), 'this week' (last 7 days), 'last N' or a bare number (most recent N sessions), or empty (defaults to last 10).

Can I use this to hand off to another agent?

Yes. The recap provides a structured summary of recent work that another agent can review before continuing the project.

Full instructions (SKILL.md)

Source of truth, from rohitg00/agentmemory.


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

Quick start

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.

Why

Only summarize sessions and observations the tools returned. An empty window is a real answer, not a prompt to invent activity.

Workflow

  1. Parse $ARGUMENTS: today = current local date; this week = last 7 days; last <n> or bare numeric = most recent N; empty = last 10.
  2. Call memory_sessions, filter to the current project (match cwd against the working directory), apply the window, sort by startedAt descending.
  3. Group survivors by local calendar date (YYYY-MM-DD).
  4. Per session list id (first 8), title or first prompt, observation count, status. Indent 2-3 highlights (importance >= 7) from memory_recall.
  5. End with "N sessions across M days, K observations."

Anti-patterns

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."

Checklist

  • Window parsed correctly from the argument.
  • Sessions filtered to the current project's cwd.
  • Highlights come from memory_recall, not paraphrase.
  • Totals line reflects the actual counts shown.

See also

  • handoff, session-history, recall: same session data, different lens.

Troubleshooting

See ../_shared/TROUBLESHOOTING.md if memory_sessions or memory_recall is not available.