Summarize and review what changed while you were away. Use after a weekend, vacation, or flight to check missed PRs, git commits, Linear tickets, and meetings — one prioritized brief, not a firehose.
SkillScore73Maintained
On-demandOn-demand: invoked explicitly — never occupies your agent's context until called.
◆Project Management pack
Last verified 8/19/2026
What it changes
Passed 12 of 17 test cases with the skill, and 5 of 17 without it.
Without skill27%
With skill73%
Checks it passed that the model alone missed
Uses the Sonnet model for the subagent.
Queries Calendar MCP tools inside the main orchestrator session.
Specifies subagent_type as catchup-runner when invoking the agent.
and 9 more in the full report
10 fixed6 passed either way6 still failing0 broke
Pass-rate lift
+45 pp
Tokens
+36%
Agent turns
0%
Response time
-57%
Model gemini-3.6-flashMeasured 8/19/2026v116 of 22 cases passed with skill · 17 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 10
Prompt
Where should the catchup brief markdown file be saved on disk, and what date format should be used in its filename?
What was checked, without and with the skill
Checked
Without skill
With skill
Specifies the output path under .claude/catchup/ in the workspace root directory.
Missed
Passed
Uses local timezone date format YYYY-MM-DD for the brief filename.
Passed
Passed
case-09 · gemini-3.6-flash · 8/19/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md129 lines5 files
Catchup — Async-Team Return Briefing
You've been away. This skill is a thin orchestrator: it resolves
the window + sources here, then delegates the I/O fan-out, impact
analysis, and brief assembly to the catchup-runner agent (Sonnet) so
your (often Opus) session does not pay for summarization. You only
print what the agent returns.
Usage
/catchup # since you were last active
/catchup --since "friday"
/catchup --since "2h" --focus reviews-requested
/catchup --since last-commit --depth deep
/catchup --scope all # include cross-repo pings/reviews
Default is repo-scoped: every GitHub signal (reviews requested,
notifications, mentions) is filtered to the repo you ran it in. Pass
--scope all to also include cross-repo activity, which is then listed
in its own separate section — never mixed into this repo's lists.
Iron Laws
Delegate the heavy work — spawn catchup-runner (sonnet) for
fan-out + assembly. Do NOT run the gh/git fan-out in this
session; that defeats the cost/speed purpose.
Resolve the window here, once — the agent must never re-resolve
it. Pass absolute SINCE_* values.
MCP runs here, not in the agent — Linear/Calendar MCP tools are
unreliable in subagents. If present, fetch in this context and pass
the text to the agent; else mark absent.
Validate --since before any shell — match the grammar; on no
match fall back to 24h and note the assumption.
Stop after the brief — print the agent's summary, never
auto-transition to another command.
Repo-scoped by default — pass SCOPE=repo unless the user
passed --scope all. A brief run inside one repo must not leak
another repo's reviews/notifications. Cross-repo is opt-in only.