session-recap
Skill2 starsChanged 4 months agoNo licenceView on GitHub
Read a Claude Code session's transcript and produce two markdown artifacts plus a meta.json: a scannable Summary (TL;DR, key terms, files, decisions, open threads) and a complementary Detailed Note (full glossary, chronological flow, command-by-command annotations, pitfalls). The output language follows the watched session's dominant language (>= 50% Japanese characters → Japanese, otherwise English; overridable via --language). Standalone — pass a session ID, or omit to pick from recent sessions in the current directory. After generation, dispatches a configurable chain of follow-up skills (default ["recap-to-notion"]) read from ~/.claude/session-recaps/.recap-config.json. Owns the manifest schema and runs cleanup of confirmed-uploaded local recap dirs past retention. Read-only on the transcript itself. Use when the user says "session recap" / "セッションのまとめ" / "セッションサマリ" / "学びをまとめて" / "用語集を作って" / "summarize the session" / "recap session" / "session note" / "セッションのノート" / "/session-recap" / "セッション解説まとめ" / "recap掃除" / "recap cleanup" / "古いrecap削除".
- Deletes or force-pushes
- Commits and pushes
5 other projects use a version of this.
Adopted by
Most recently taken up by
- thistleknot/skillstheir own version, first seen Nov 8, 2026
- RouanetClement/claude-skillstheir own version, first seen Oct 15, 2026
- blair-keck/claude-skillstheir own version, first seen Oct 13, 2026
- topness-msft/crowdhum-plugintheir own version, first seen Jul 8, 2026
- sonichi/sutandotheir own version, first seen May 17, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- sonichi/sutando★ 396same name
- blair-keck/claude-skills★ 0same name
- RouanetClement/claude-skills★ 0same name
- thistleknot/skills★ 0same name
- topness-msft/crowdhum-plugin★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository58 other files it gives its agents.
- AGENTS.mdAGENTS.md
- adversarial-panelSkill
- agents-initSkill
- agent-swarmSkill
- chrome-useSkill
- codex-cliSkill
- codex-serverSkill
- confluenceSkill
- deepenSkill
- dev-workflowSkill
- diagnoseSkill
- dotnet-seniorSkill
- e2e-testSkill
- en-to-ja-explainerSkill
- figma-shot-boardSkill
- gdrive-cliSkill
- grill-meSkill
- grill-to-implSkill
- grill-with-docsSkill
- handoffSkill
- improve-codebase-architectureSkill
- japanese-tech-writingSkill
- jira-cliSkill
- local-skill-factorySkill
- logo-imageSkill
- my-gdriveSkill
- my-skill-factorySkill
- naturalize-jaSkill
- natural-japaneseSkill
- notion-cliSkill
- openai-cliSkill
- orch-qaSkill
- parallel-investigateSkill
- playwright-cliSkill
- pm-reviewSkill
- postmortemSkill
- prd-councilSkill
- prototypeSkill
- pr-reviewSkill
- recap-to-notionSkill
- review-localSkill
- scenario-genSkill
- self-pr-reviewSkill
- session-handoverSkill
- session-watchSkill
- skill-improveSkill
- slack-cliSkill
- slack-to-ticketSkill
- subagent-genSkill
- tddSkill
- test-scenarioSkill
- to-prdSkill
- triageSkill
- ui-spec-simSkill
- well-arch-costSkill
- well-arch-reliabilitySkill
- well-arch-securitySkill
- zoom-outSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
27 rules. 0 are common, 10 are distinctive, and 17 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
10
Distinctive
This author's own choices. Worth a look.
17
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.