agentleFS
Sign inStart free
ArchieeRArchieeR/claude-skills/skills/recap/SKILL.md

recap

Skill0 starsChanged 3 months agoMITView on GitHub

Produce a concise table-format recap/overview of the current session — what was done, its status, decisions made, and open follow-ups. Works in ANY session type (coding, debugging, research, GTM, ops, planning). Use when the user types /recap, /table, or asks for "a table", "recap", "overview", "where are we", "catch me up", "summary of what we did".

44 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use glossary, orchestrate and 7 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.
  • Microsoft AzureSkill

    glossary

    Short glossary of domain terms used by the team.

    Also in 3 projects that use this

  • varun29ankuSSkill

    orchestrate

    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

  • sunnyclinches44Skill

    explain

    Explains code using real-world analogies and ASCII diagrams

    Also in 3 projects that use this

  • Microsoft AzureSkill

    build

    Build the TypeSpec Rust emitter from source. Run this after cloning the repo, after pulling changes, or when TypeScript source files have been modified.

    Also in 3 projects that use this

  • nicolasestremSkill

    brainstorm

    Structured idea generation and solution exploration with systematic analysis.

    Also in 3 projects that use this

  • BlockSkill

    plan

    Draft a TDD, PRD, or lightweight plan in the conversation without committing it.

    Also in 3 projects that use this

The file

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 38 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
  1. Distinctive:

    Dense: No prose around the tables beyond the TL;DR.

    line 35
  2. Distinctive:

    If invoked mid-task, recap covers work-so-far and marks the live task 🟡/⏳.

    line 41

“Common” is measured: kept by at least 6 in 10 of the 38 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Recap

Produce a tight, scannable table recap of the current session so the user sees at a glance what happened, what state each thing is in, and what's left. Adapt to the session type — don't force irrelevant rows. This is a glance, not a report.

Output format

Lead with a one-line TL;DR (≤1 sentence). Then up to three tables, omitting any that would be empty:

1. What happened (always)

#ItemWhat happenedStatus
  • Status = emoji + word: ✅ done · 🟡 in progress · ⏳ waiting/running · 🔴 blocked/failed · 💡 noted/idea
  • One row per meaningful unit of work, most-important first. Cells ≤ ~12 words.
  • Anchor with concrete refs where useful: file:line, commit SHA, ticket ID, run ID, URL.

2. Decisions (only if any were made)

DecisionChoiceWhy (≤8 words)

3. Open / next (only if anything remains)

ItemOwnerNote
  • Owner = who's on the hook: User / Claude / CI / external.

Rules

  • Faithful, not flattering. Include blocked, failed, skipped, and uncertain items — never hide them. If something's unverified, say so in the cell ("logic-proven, not run live").
  • Pull from the actual session, not assumptions or memory.
  • Dense. No prose around the tables beyond the TL;DR. No restating cells in sentences.
  • Trivial/short session → a single small table is fine; don't pad.
  • End with exactly one line: "Want detail on any row, or should I action any of the open items?"

Notes

  • This is a presentation skill — it does not change code or state, only summarises. If the user wants follow-ups actioned, that's a separate step they trigger.
  • If invoked mid-task, recap covers work-so-far and marks the live task 🟡/⏳.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free