Agent skill

Session Recap

by rohitg00 in rohitg00/agentmemory

Summarizes recent agent sessions for the current project by date, with each session's title, status, observation count and top highlights from memory.

Apache-2.0Auto-check passedAgent Workflows

Install Session Recap

skills CLI
$ npx skills add rohitg00/agentmemory --skill recap -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install rohitg00/agentmemory recap --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/rohitg00/agentmemory.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugin/skills/recap .claude/skills/recap && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
recap
GitHub stars
29k
Token cost
~510 tokens
SKILL.md length
206 words
Files
2
Skills in repo
17
Repo updated
First seen
Licence
Apache-2.0

At a glance

Summarizes recent agent sessions for the current project by date, with each session's title, status, observation count and top highlights from memory.

  • Works in 5 steps: Parse $ARGUMENTS: today = current local… → Call memory_sessions, filter to the… → Group survivors by local calendar date… → …
  • Asking what you worked on today or this week in the current project
  • SKILL.md covers Quick start, Why, Workflow and Anti-patterns, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

When you ask for a recap, the agent reads the time window from your request: today, this week, the last N sessions, or the most recent ten if you give nothing. It lists sessions with `memory_sessions`, keeps only those whose working directory matches the current project, applies the window, sorts newest first and groups them by local calendar date.

Each session shows a short id, a title or first prompt, how many observations it holds and its status, followed by two or three high-importance highlights pulled with `memory_recall`. The output ends with a totals line for sessions, days and observations. The skill is strict that only returned data is summarized: an empty window gets a plain statement that no sessions exist, never invented activity. An examples file ships with it.

When your agent uses it

  • Asking what you worked on today or this week in the current project
  • Getting a dated rollup of the last several agent sessions
  • Re-orienting at the start of a day before picking work back up

Example prompts

  • “Recap what we did this week.”
  • “Give me a recap of the last 5 sessions in this project.”
  • “What have we been doing today?”

Requirements

  • The agentmemory tools `memory_sessions` and `memory_recall`

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Parse $ARGUMENTS: today = current local date; this week = last 7 days;
  2. Call memory_sessions, filter to the current project (match cwd against the
  3. Group survivors by local calendar date (YYYY-MM-DD).
  4. Per session list id (first 8), title or first prompt, observation count,
  5. End with "N sessions across M days, K observations."

What it can do on your machine

Read from SKILL.md and the folder at commit 007a1a7. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are json).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Session Recap loads about 510 tokens when it runs. Until then it costs about 60 tokens; SKILL.md has 206 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~60
When it runs · the whole SKILL.md, loaded when a task matches
~510

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from rohitg00/agentmemory at commit 007a1a7, republished under its Apache-2.0 licence (© rohitg00). 206 words, ~510 tokens.

Download SKILL.mdSave it as .claude/skills/recap/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
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

json
memory_sessions { "limit": 30 }

Then per surviving session: memory_recall { "query": "<top concepts>", "limit": 3 }.

Expected output:

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

© rohitg00, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in plugin/skills/recap of rohitg00/agentmemory.

  • SKILL.md
  • EXAMPLES.md

Open the folder on GitHubat commit 007a1a7

Compare with similar skills

Session Recap next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Session Recap compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Session Recap this skillrohitg00/agentmemory29k—~510Automated safety check: PassApache-2.0
Coding Agent Session Findercode-yeongyu/oh-my-openagent70k1 repos~2.8kAutomated safety check: PassCustom licence
Beads Task Memorygastownhall/beads28k—~1.2kAutomated safety check: PassMIT
Session History Searchslopus/happy24k—~3.1kAutomated safety check: PassMIT
Memori Long-Term MemoryMemoriLabs/Memori17k—~2kAutomated safety check: NotesCustom licence
Project Timeline Reportthedotmack/claude-mem98k1 repos~3.1kAutomated safety check: PassApache-2.0

Similar skills

  • Coding Agent Session Finder

    code-yeongyu/oh-my-openagent

    Finds, reads and reconstructs past coding-agent sessions across Codex, Claude, OpenCode, Senpi and many other local agent logs.

    70k GitHub starsUsed in 1 repo~2.8k tokens
    Agent WorkflowsAuto-check passed
  • Beads Task Memory

    gastownhall/beads

    Tracks multi-session work with dependencies in the bd issue tracker so the agent can find ready tasks and recover its context after conversation compaction.

    28k GitHub stars~1.2k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed
  • Searches past Claude Code, Codex and Cursor sessions and summarizes what was worked on, tried or decided, using extraction scripts instead of reading raw logs.

    24k GitHub stars~3.1k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed
  • Memori Long-Term Memory

    MemoriLabs/Memori

    Connects Claude Code to Memori Cloud for long-term memory, recalling stored context before substantive replies and saving new context afterward.

    17k GitHub stars~2k tokensUpdated 6 days ago
    Agent WorkflowsAuto-check: notes
  • Project Timeline Report

    thedotmack/claude-mem

    Writes a narrative Journey Into report on a project's whole development history, built from the timeline that claude-mem has recorded.

    98k GitHub starsUsed in 1 repo~3.1k tokens
    Agent WorkflowsAuto-check passed
  • Mindmemos CLI

    mindscale-noah/MindMemOS

    Give an AI agent persistent, cross-session long-term memory through MindMemOS.

    1k GitHub starsUsed in 1 repo~3.4k tokens
    Agent WorkflowsAuto-check passed

More from rohitg00/agentmemory

All 17 skills in this repo
  • Sets up and troubleshoots a local agentmemory install, covering the MCP connection, environment variables, ports, authentication and optional feature flags.

    29k GitHub stars~1k tokensUpdated 2 days ago
    Auto-check: notes
  • Commit Context Lookup

    rohitg00/agentmemory

    Traces a file, function or line back to the agent session behind its current commit, using git blame and a memory lookup, and reports only what the records show.

    29k GitHub stars~522 tokensUpdated 2 days ago
    Auto-check passed
  • Agent Commit History

    rohitg00/agentmemory

    Lists recent git commits linked to agent sessions, filterable by branch, repository or a result limit, showing the session id and observation count behind each one.

    29k GitHub stars~524 tokensUpdated 2 days ago
    Auto-check passed
  • Agentmemory Forget

    rohitg00/agentmemory

    Deletes chosen memories from agentmemory only after showing the matches and getting an explicit yes, for privacy requests and cleanup of outdated notes.

    29k GitHub stars~612 tokensUpdated 2 days ago
    Auto-check passed
  • Session Handoff Resume

    rohitg00/agentmemory

    Resumes the most recent agent session for the current directory, leading with any question left unanswered and ending with a concrete next step.

    29k GitHub stars~678 tokensUpdated 2 days ago
    Auto-check passed
  • Lesson Memory Recorder

    rohitg00/agentmemory

    Distills a user correction or hard-won rule into a confidence-weighted lesson that resurfaces automatically before similar future work.

    29k GitHub stars~721 tokensUpdated 2 days ago
    Auto-check passed

Categories

Questions about Session Recap

What does Session Recap do?

Summarizes recent agent sessions for the current project by date, with each session's title, status, observation count and top highlights from memory. When you ask for a recap, the agent reads the time window from your request: today, this week, the last N sessions, or the most recent ten if you give nothing. It lists sessions with `memory_sessions`, keeps only those whose working directory matches the current project, applies the window, sorts newest first and groups them by local calendar date.

When should I use Session Recap?

Session Recap fits situations like: asking what you worked on today or this week in the current project; getting a dated rollup of the last several agent sessions; re-orienting at the start of a day before picking work back up.

How do I install Session Recap in Claude Code?

Run `npx skills add rohitg00/agentmemory --skill recap -a claude-code`. Or copy the skill folder (plugin/skills/recap in rohitg00/agentmemory) into .claude/skills/recap in your project. Claude Code loads it when a task matches its description.

How do I install Session Recap in Codex?

Run `npx skills add rohitg00/agentmemory --skill recap -a codex`. Or copy the skill folder (plugin/skills/recap in rohitg00/agentmemory) into .agents/skills/recap in your project. Codex loads it when a task matches its description.

Can I use Session Recap in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add rohitg00/agentmemory --skill recap -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/recap, .gemini/skills/recap, .github/skills/recap and .opencode/skills/recap in your project.

What does Session Recap need to run?

SKILL.md names no scripts, command-line tools or credentials: Session Recap is instructions for the agent only. Our summary lists: The agentmemory tools `memory_sessions` and `memory_recall`.

Does Session Recap access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Session Recap safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Session Recap use?

Session Recap is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Session Recap use?

About 510 tokens (SKILL.md is roughly 2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Session Recap?

Skills that share tags, products or a category with Session Recap: Coding Agent Session Finder (code-yeongyu/oh-my-openagent, 70k stars), Beads Task Memory (gastownhall/beads, 28k stars), Session History Search (slopus/happy, 24k stars) and Memori Long-Term Memory (MemoriLabs/Memori, 17k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Session Recap?

rohitg00 (a GitHub user) maintains it in rohitg00/agentmemory, which has 29,222 GitHub stars. The repository holds 17 skills in this directory. The repository was last updated on October 6, 2026.

Source: rohitg00/agentmemory on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.