catch-up
Skill0 starsChanged 41 days agoMITView on GitHub
Use when the user asks to be caught up on the current session - "/catch-up", "catch me up", "where are we", "where did we leave off", "what's the status", "recap", "what do you need from me" - typically after stepping away, switching between agent tabs, a context compaction, or returning to a long-running session.
21 other projects use a version of this.
Adopted by
Most recently taken up by
- whyashthakker/estacktheir own version, first seen Nov 8, 2026
- hype-sports/hype-assistant-plugintheir own version, first seen Nov 8, 2026
- hidenobunagai/astacktheir own version, first seen Nov 8, 2026
- requie/endostacktheir own version, first seen Nov 8, 2026
- JeffreyFerreiras/ai-skillstheir own version, first seen Nov 1, 2026
- zanellig/skillstheir own version, first seen Nov 1, 2026
Used with
Projects with it also use in-your-own-words, bro and 3 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.
drafaelSkillin-your-own-words
Restate the user's goals and the problem they are trying to solve to check understanding. Manual invocation only; use when the user explicitly invokes in-your-own-words or requests this understanding check. Do not solve the task or rewrite the assistant's last answer.
Also in 3 projects that use this
MicrosoftSkillbro
Re-explain the previous assistant message in a much simpler way, for when the reply made you go 'bro what'. Use /bro to get a simpler version of the last answer in Plain Language + Chicago Manual of Style, with diagrams where they help.
Also in 3 projects that use this
- MicrosoftSkill
blast-radius
Assesses network dependency and shared-infrastructure exposure. Use when the user asks which services, customers, SLA policies, routes, or redundant links are affected by a network fault.
Also in 3 projects that use this
termdockSkillrecall
Retrieves cross-session memories about past decisions, lessons, and patterns. Use when user asks about prior work, past decisions, or mentions a feature. Triggers include check memory, what did we decide, how did we solve.
Also in 3 projects that use this
photon-groveSkillunslop
Detects and rewrites generic, overly polished, or AI-sounding prose while preserving meaning. Use when the user asks to "unslop", humanize, de-AI, tighten, or review whether writing sounds generated.
Also in 4 projects that use this
Other versions21 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 21
- petekp/claude-code-setup★ 48same name
- ARCASSystems/FounderOS★ 7same name
- david-vrba/claude-power-skills★ 4same name
- requie/endostack★ 4same name
- matiopala/skills★ 2same name
- chendaniely/skills★ 1same name
- hidenobunagai/astack★ 1same name
- JeffreyFerreiras/ai-skills★ 1same name
- median-labs/close-the-books★ 1same name
- TheKontextCo/kontext-claude-plugin★ 1same name
11 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 repository34 other files it gives its agents.
- afkSkill
- apple-contactsSkill
- apple-devSkill
- apple-notesSkill
- apple-photosSkill
- bug-huntSkill
- cherriSkill
- chrome-controlSkill
- claude-sessionsSkill
- coordinatorSkill
- discountsSkill
- forge-skillSkill
- groupmeSkill
- herdr-crewSkill
- iconsSkill
- imsgSkill
- language-selectionSkill
- laterSkill
- mac-controlSkill
- nix-mechanicsSkill
- notion-cliSkill
- posthogSkill
- quotaSkill
- redditSkill
- rustSkill
- scoutSkill
- semverSkill
- social-contentSkill
- spotifySkill
- travelSkill
- validate-ideaSkill
- verdictSkill
- web-reconSkill
- whatsappSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 20 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 42
Use a few sentences per item when needed to make the decision clear.
- Very specific: line 50
Read the session from your own context.
- Distinctive: line 54
Verify perishable facts instead of recalling them, read-only only: git status -sb in every repo the session touched, your background task …
“Common” is measured: kept by at least 6 in 10 of the 20 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
Catch-up
One read that lets the user resume this session without scrolling back. It reports the session's state; it never continues the work.
Output
Exactly two headed sections, in this order. Put most of the detail in Needs you, so the user can answer accurately without scrolling back.
Summary
One short paragraph, usually 2-4 sentences, combining completed outcomes, work in progress, remaining work and loose ends. Include the most useful result or evidence link, anything still running, and material blockers or unverified work. Distinguish finished work from plans. Compress routine checks and cleanup details; do not recreate the old sections as labeled bullets.
Needs you
A numbered list of every unresolved decision, approval, question or manual step only the user can handle, including earlier requests still unanswered. Order blockers first. Give each item enough context to stand alone:
- State the specific question or action, what it concerns, and why their input is needed. Explain what their answer will enable or change.
- For choices, use lettered options with the recommendation first, its reason, and the meaningful tradeoffs. Make replies like "1a, 2b" possible. Do not invent choices when a direct answer is needed.
- For missing information, specify the exact details needed and a useful example or answer format when it would remove ambiguity.
- For manual steps, give the relevant link or location, concise instructions, and what result the user should report back.
- Carry forward prior answers and approvals; ask only for what is still missing. Never turn work the agent can do into a request for the user.
Use a few sentences per item when needed to make the decision clear; omit implementation details that do not affect the answer. If nothing needs the user, write "Nothing needed from you."
End the turn after these two sections. Do not continue the underlying work.
Gathering
- Read the session from your own context. After a compaction the summary
drops detail; the transcript is the record (Claude Code:
~/.claude/projects/<cwd-slug>/<session-id>.jsonl) - search it for questions you asked and the replies. - Verify perishable facts instead of recalling them, read-only only:
git status -sbin every repo the session touched, your background task list and the processes you started, the current state of any ticket you were updating. - Report what is true now. Something said or planned but not done goes under the Summary as pending or unverified, never as completed.
Common mistakes
| Mistake | Instead |
| A long status report followed by terse questions | Brief Summary, self-contained Needs you items |
| A choice without context or consequences | Explain what changes, recommend an option and why |
| Calling written-but-unverified or unpushed work done | Say what verification or delivery remains |
| Hiding a needed approval in the Summary | Put the actionable request in Needs you |
| Forgetting a running command or watcher | Check current processes and mention them in the Summary |
| Asking again for an answered question | Preserve the answer and request only missing input |
| Answering questions or resuming work after the recap | Stop; the user's reply decides what happens next |
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.