catchup
Rebuild the human's lost context on a project from live state, in plain language: what needs them, what changed, what new words mean. Use when the human returns after a gap, says they can't follow the project anymore, asks what happened or what a term means, or before deciding what to do next when their mental model is stale. Read-only; it briefs, it does not act.
- Installs
- 1.2K
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/lilmgenius/paperthin --skill catchup- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads catchup automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Catch the human up at their eye level, from state, not from memory.
Goal
catchup is the re-entry point for a lost human. Long agent cycles coin words, rename files, run
experiments, and make calls faster than the owner can follow. Before any next action makes sense,
the owner's mental model must be reloaded. catchup reads the live project state and returns a
briefing a person with zero retained context can act on. It runs before the next move gets decided:
catchup restores the map, so that decision starts from truth instead of a stale memory of it.
Workflow
- Read live state only: recent file mtimes, git log/diffs, plan and state docs, re0-memo notes, task boards. Never brief from conversation memory alone — memory is what drifted.
- Anchor on the human's last touch (their last message, judgment, or commit). Everything after that point is the delta; everything before it is assumed known and stays out.
- Compose in decision order, not chronological order:
- Needs you — decisions, judgments, or inputs only the human can give, each self-contained enough to act on without opening another file.
- Changed while you were away — outcomes, not process. "The plan's scoring rule was replaced" beats "I ran three analysis passes."
- New words — every term coined or repurposed since their last touch, one line each, with where it lives. Skip terms they already used themselves.
- Gloss on first use: any project-specific term appearing in the briefing gets an inline plain-language aside at its first occurrence, even if a glossary section follows.
- Keep the default short (a screen or less). End with drill-down offers per section, not with everything expanded.
Rules
- State-grounded: every claim traces to a file, commit, or artifact the human can open. No "as we discussed."
- Read-only on the project.
catchupbriefs; it does not fix, rename, or decide. - The ask comes first. A briefing that buries the one question needing the human is a log.
- Outcome voice, not journey voice. Narrating the agent's process is self-report, not briefing.
- Silence the settled: closed decisions and healthy metrics get one line or none.
- Honest completeness: "done" means verified done; "moved" is not "reconciled"; say which.
- Do not re-explain terms the human demonstrably knows (they used them first).
Verification
Before finishing:
- Cold-read the briefing: no sentence requires pre-gap memory or an unglossed coined term to parse.
- The "needs you" items are each actionable without opening another file.
- Every claim has a checkable source (file, commit, artifact path).
- It fits on a screen, with expansion offered rather than delivered.
FAQ
What does the catchup skill do?
Rebuild the human's lost context on a project from live state, in plain language: what needs them, what changed, what new words mean. Use when the human returns after a gap, says they can't follow the project anymore, asks what happened or what a term means, or before deciding what to do next when their mental model is stale. Read-only; it briefs, it does not act.
How do I install catchup?
Run npx skills add https://github.com/lilmgenius/paperthin --skill catchup in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/catchup/ (personal) or .claude/skills/catchup/ (project).
Which AI agents can use catchup?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is catchup safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains catchup?
It is published by lilmgenius in lilmgenius/paperthin. It has 1,212 recorded installs.
More from lilmgenius/paperthin
dedash
lilmgenius/paperthin
Remove em-dashes and the dashes standing in for them from a user-owned scope, reading each occurrence in context and choosing the punctuation or wording that fits.
ssotize
lilmgenius/paperthin
Audit and consolidate a fact that's scattered across places into one canonical source, after approval, and replace the rest with references. Use when asked to find duplication, check consistency, locate the source of truth, deduplicate, consolidate, unify, or establish SSOT across artifacts or platforms. Starts read-only, reports the map and plan, then mutates only after explicit approval.
shower
lilmgenius/paperthin
Cold-read the artifact you're focused on from a fresh, zero-context sub-session to confirm it stands on its own — a shower-thought reset for accumulated session bias. Use when a long session has worn away your fresh eyes and you can no longer tell whether the artifact in focus is clear to someone with no prior context; before a handoff, publish, or merge; or when you want a clean-room comprehension smoke test. Spawns a separate context-free reviewer; it diagnoses, it does not fix.
hate
lilmgenius/paperthin
Attack a plan, design, or argument like you want it to fail before you commit real effort — return the single load-bearing objection and the cheapest experiment that would prove it matters, not a checklist. User-invoked on purpose: a hate-it reflex always in the agent's reach would bias it toward demolition. Weighs many failure axes but owns the synthesis to one root.
factchk
lilmgenius/paperthin
Verify reality-grounded claims against external sources in both directions before they ship — could the 'absurd' be real, could the 'obvious' be false or long-established? Use whenever an artifact, or the sentence you are about to write, asserts something as plausible, realistic, absurd, novel, or impossible from intuition rather than a checked source; before relying on a factual claim in prose, a design rationale, a research claim, or a plan. Fires on metacognitive doubt — when you can't actually know, verify instead of trusting the feeling. Scans read-only, then fixes the clear errors or flags the judgment calls; leaves deliberate fiction alone.
re0
lilmgenius/paperthin
Refresh an existing artifact into the current best v0. Use when the user asks to clean up, sync up, dedupe, de-noise, smooth, rewrite, or update an artifact after iteration; when nearby artifacts may have drifted; or when changes in one place should be reflected across related artifacts while keeping the result minimal.
Popular other skills
hyperframes-cli
heygen-com/hyperframes
The HyperFrames CLI by job - scaffold, check, look at frames, edit the timeline, preview, render locally or in the cloud, publish, project history - plus reading its JSON and recovering from build or render failures.
triage
mattpocock/skills
Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.
ask-matt
mattpocock/skills
Ask which skill or flow fits your situation. A router over the skills in this repo.
to-questionnaire
mattpocock/skills
Turn a decision you can't fully answer into a questionnaire for someone else to fill in.
loop-me
mattpocock/skills
Grill me about specs for the workflows I want to build, within this workspace.