recap
Skill24 starsChanged 19 days agoMITView on GitHub
Quick summary of what you covered last session
45 other projects use a version of this.
Adopted by
Most recently taken up by
- web3illy/private-second-brain-skillstheir own version, first seen Nov 16, 2026
- Integralist/agent-skillstheir own version, first seen Nov 14, 2026
- mel0nyrame/skillstheir own version, first seen Nov 8, 2026
- delorenj/skillstheir own version, first seen Nov 7, 2026
- acegalaxy-co/ace_commons-ccswitch-clitheir own version, first seen Nov 1, 2026
- kanalias/ace_commons-ccswitch-clitheir own version, first seen Nov 1, 2026
Used with
Projects with it also use orchestrate, brainstorm and 4 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
varun29ankuSSkillorchestrate
This skill should be used when the user asks to 'orchestrate a task', 'break down work into parallel agents', 'coordinate subtasks', 'run agents in parallel', or mentions 'multi-agent'. Decomposes complex tasks into tracked subtasks, dispatches parallel subagents, and coordinates until completion.
Also in 4 projects that use this
nicolasestremSkillbrainstorm
Structured idea generation and solution exploration with systematic analysis.
Also in 3 projects that use this
BlockSkillplan
Draft a TDD, PRD, or lightweight plan in the conversation without committing it.
Also in 3 projects that use this
SentrySkillcommit
Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.
Also in 3 projects that use this
SentrySkillreview
Fixture review skill.
Also in 3 projects that use this
MicrosoftSkillhandoff
Compact the current conversation into a handoff document for another agent to pick up.
Also in 3 projects that use this
Other versions45 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 45
- first-fluke/fullstack-starter★ 226same name
- backnotprop/bro★ 182same name
- benoror/obsidianos_work★ 166same name
- Soul-Brews-Studio/arra-oracle-skills-cli★ 121same name
- mbwsims/claude-universe★ 71same name
- Integralist/agent-skills★ 29same name
- delorenj/skills★ 17same name
- ivklgn/ai-kit★ 12same name
- ivklgn/bag-of-skills★ 12same name
- Jamaalx/claude-chat-namer★ 5same name
35 more not listed
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 repository23 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- architectureSkill
- audit-contentSkill
- benchmarkSkill
- break-itSkill
- buildSkill
- challengeSkill
- code-reviewSkill
- compareSkill
- debug-ragSkill
- evaluateSkill
- explainSkill
- fixSkill
- glossarySkill
- journalSkill
- lessonSkill
- paper-reviewSkill
- quizSkill
- roadmapSkill
- sandboxSkill
- startSkill
- triageSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 4 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 39 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Read the following files to reconstruct the last session:
- Very specific: line 19
If no progress data exists, say: "No previous session found.
- Distinctive: line 23
Keep it to 5-8 lines max. Cover:
- Very specific: line 46
If mid-module: /lesson to continue
- Very specific: line 47
If they just finished a module: /quiz to test understanding
- Very specific: line 48
If quiz scores were low: /explain [weak topic] to review
- Distinctive: line 49
If they wrote journal notes with questions: address the question briefly
- Distinctive: line 51
Keep it short. The whole recap should fit in one screen.
“Common” is measured: kept by at least 6 in 10 of the 39 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
Recap: What You Learned Last Time
Give the learner a fast, useful summary of their most recent session so they can pick up where they left off.
Step 1: Load Session History
Read the following files to reconstruct the last session:
progress/module-tracker.md— find the most recently completed lessons (by date)progress/quiz-results.md— any quizzes taken recentlyprogress/journal.md— any notes the learner wroteprogress/learner-profile.md— current module and track
If no progress data exists, say: "No previous session found. Run /start to begin your journey."
Step 2: Summarize Last Session
Keep it to 5-8 lines max. Cover:
- What you worked on — which lesson(s), quiz, or challenge
- Key concepts — the 2-3 main ideas from that session, in plain language
- Where you stopped — what's next in the track
Format:
Last Session Recap
==================
You worked on: [lesson/quiz/challenge name]
Key concepts:
- [concept 1 in one sentence]
- [concept 2 in one sentence]
- [concept 3 in one sentence]
Next up: [next incomplete lesson or suggested action]Step 3: Suggest Next Action
Based on where they left off, suggest one clear next step:
- If mid-module:
/lessonto continue - If they just finished a module:
/quizto test understanding - If quiz scores were low:
/explain [weak topic]to review - If they wrote journal notes with questions: address the question briefly
Keep it short. The whole recap should fit in one screen.
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.

