session-summary
Skill3 starsChanged 24 days agoMITView on GitHub
Skill for summarizing the current session's context, including completed tasks, technical decisions, and next steps. Use this skill when you need to create a handover document for a new session, switch contexts without losing critical information, or document what was accomplished before ending a session.
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
Document completed tasks and technical decisions
- Distinctive: line 31
When asked to summarize the session, structure your response as follows:
“Common” is measured: kept by at least 6 in 10 of the 6 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.
Files
Session Summary & Handover
You are an expert at context management and project continuity. Your goal is to capture the essence of the current development session so that work can continue seamlessly in a fresh environment.
When to Use
Trigger scenarios — use this skill when the user asks to:
- Summarize the current session for handover to a new session
- Document completed tasks and technical decisions
- Switch contexts without losing critical information
Your Responsibilities
- Analyze the current state: Review the recent interactions, file changes, and accomplished goals.
- Summarize Key Information:
- Goal: What was the main objective of this session?
- Progress: What exactly was achieved? (Files created, bugs fixed, features implemented)
- Context: Key technical decisions made, environment variables set, or specific constraints discovered.
- Open Issues: Any unresolved errors, blocked tasks, or partial implementations.
- Define Next Steps: A clear, prioritized list of what needs to be done immediately in the next session.
- Generate Handover Prompt: detailed prompt that the user can paste into the next session to restore context.
Handover Format
When asked to summarize the session, structure your response as follows:
1. Session Snapshot
- Objective: ...
- Status: [Completed / In-Progress / Blocked]
2. Accomplishments
- ...
- ...
3. Technical Context
- ...
4. Next Session To-Do
- Task 1
- Task 2
5. Restore Prompt (Copy & Paste this into new session)
[CONTEXT RESTORATION]
Project Path: <Current Path>
Last Session Summary:
<Insert Summary Here>
Immediate Tasks:
<Insert Next Steps Here>
Please review the current files and continue from where we left off.Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 10
- felvieira/claude-skills-fv★ 27same name
- microsoft/aibast-agents-library★ 8same name
- tatsoft-llc/Claude-Code-Skills★ 2same name
- EasyJoy-Technologies/openclaw-skills★ 1same name
- lldwb/lldwb-claude-skills★ 1same name
- ryusuke-ai/argus★ 1same name
- sss-hust/skills★ 1same name
- Cal-Starfur/claude-skills★ 0same name
- kwana117/claude-skills★ 0same name
- System-Error-Worldwide/the-loop★ 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 repository37 other files it gives its agents.
- api-designSkill
- database-designSkill
- design-patternSkill
- enterprise-javaSkill
- frontend-reactSkill
- frontend-svelteSkill
- frontend-vueSkill
- git-guruSkill
- go-developmentSkill
- javascript-typescriptSkill
- product-managementSkill
- python-developmentSkill
- swift-developmentSkill
- swiftui-developmentSkill
- system-architectureSkill
- tech-documentationSkill
- testingSkill
- xcode-managementSkill
- api-designSkill
- database-designSkill
- design-patternSkill
- enterprise-javaSkill
- frontend-reactSkill
- frontend-svelteSkill
- frontend-vueSkill
- git-guruSkill
- go-developmentSkill
- javascript-typescriptSkill
- product-managementSkill
- python-developmentSkill
- session-summarySkill
- swift-developmentSkill
- swiftui-developmentSkill
- system-architectureSkill
- tech-documentationSkill
- testingSkill
- xcode-managementSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.

