How do I install the Sessionlog:recap skill?

Run npx skillmds@latest add florianbuetow/sessionlog-recap in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Sessionlog:recap safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Sessionlog:recap?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Sessionlog:recap free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Sessionlog:recap?

florianbuetow (@florianbuetow) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Sessionlog:recap by florianbuetow — Agent Skill

Name: Sessionlog:recap
Author: florianbuetow

Sessionlog:recap

This skill should be used when the user asks to "recap", "brief me", "remind me", "what did we work on", "what happened last time", "catch me up on recent sessions", "sessionlog recap", "session recap", "recent session summary", "tldr sessions", or wants a quick summary of what was worked on in recent sessions for this project.

File contents

Session Recap

Read the last 3 session logs for this project and produce a concise TLDR of what was worked on.

Steps

1. Find recent sessions

project_dir="$HOME/.claude/projects/$(pwd | sed 's|/|-|g')"
sessions=$(ls -t "$project_dir"/*.jsonl 2>/dev/null | head -4)
echo "$sessions"

We grab up to 4 because the most recent one is the current session. Skip it and use the 3 before it.

2. Export each session to readable TXT

For each of the 3 previous sessions (skip the first/current one):

output_dir=$(mktemp -d)
sessions=$(ls -t "$project_dir"/*.jsonl 2>/dev/null | head -4 | tail -3)
for session_file in $sessions; do
  sid=$(basename "$session_file" .jsonl)
  "${CLAUDE_PLUGIN_ROOT}/scripts/export-session.sh" "$session_file" "$output_dir" "$sid"
done
echo "Exported to: $output_dir"

If fewer than 3 previous sessions exist, use however many are available.

3. Read each exported TXT

Read the full content of each exported claude-<session-id>.txt file from the temp directory. Read them in reverse chronological order (most recent first).

4. Generate the recap

You are summarizing recent work sessions for a developer returning to this project. Your goal is a quick, scannable recap — not a full continuity document.

Output format — print directly to the user (do NOT write to a file):

## Session Recap

Last time we worked on:

1. **<topic>** — <one-sentence summary of what was done and the outcome>
2. **<topic>** — <one-sentence summary>
3. **<topic>** — <one-sentence summary>
...

Rules:

Group by topic/theme, not by session. If two sessions touched the same feature, merge them into one bullet.
Each bullet should answer: what was done and what was the outcome (shipped, in progress, blocked, etc.)
Keep it to 3-7 bullets total. Fewer is better.
Lead with the most important/recent work.
Skip meta-activity (reading files, exploring code) — focus on actual outcomes.
If something was left incomplete or blocked, say so explicitly.
Do NOT create any files. Print the recap directly.

5. Clean up

rm -rf "$output_dir"

---name: sessionlog-recapdescription: This skill should be used when the user asks to "recap", "brief me", "remind me", "what did we work on", "what happened last time", "catch me up on recent sessions", "sessionlog recap", "session recap", "recent session summary", "tldr sessions", or wants a quick summary of what was worked on in recent sessions for this project.---# Session RecapRead the last 3 session logs for this project and produce a concise TLDR of what was worked on.## Steps### 1. Find recent sessions```bashproject_dir="$HOME/.claude/projects/$(pwd | sed 's|/|-|g')"sessions=$(ls -t "$project_dir"/*.jsonl 2>/dev/null | head -4)echo "$sessions"```We grab up to 4 because the most recent one is the *current* session. Skip it and use the 3 before it.### 2. Export each session to readable TXTFor each of the 3 previous sessions (skip the first/current one):```bashoutput_dir=$(mktemp -d)sessions=$(ls -t "$project_dir"/*.jsonl 2>/dev/null | head -4 | tail -3)for session_file in $sessions; do sid=$(basename "$session_file" .jsonl) "${CLAUDE_PLUGIN_ROOT}/scripts/export-session.sh" "$session_file" "$output_dir" "$sid"doneecho "Exported to: $output_dir"```If fewer than 3 previous sessions exist, use however many are available.### 3. Read each exported TXTRead the full content of each exported `claude-<session-id>.txt` file from the temp directory. Read them in reverse chronological order (most recent first).### 4. Generate the recapYou are summarizing recent work sessions for a developer returning to this project. Your goal is a quick, scannable recap — not a full continuity document.**Output format — print directly to the user (do NOT write to a file):**```## Session RecapLast time we worked on:1. **<topic>** — <one-sentence summary of what was done and the outcome>2. **<topic>** — <one-sentence summary>3. **<topic>** — <one-sentence summary>...```**Rules:**- Group by topic/theme, not by session. If two sessions touched the same feature, merge them into one bullet.- Each bullet should answer: *what was done* and *what was the outcome* (shipped, in progress, blocked, etc.)- Keep it to 3-7 bullets total. Fewer is better.- Lead with the most important/recent work.- Skip meta-activity (reading files, exploring code) — focus on actual outcomes.- If something was left incomplete or blocked, say so explicitly.- Do NOT create any files. Print the recap directly.### 5. Clean up```bashrm -rf "$output_dir"```

Frequently asked questions