Session summary
How to summarise a working session at a high level — what was achieved and what remains, as themed bullets with sub-bullets, splitting open items into blocked-on-the-user versus future backlog. WHEN asked to summarise or recap what was done in a session, wrap up a piece of work, hand off to someone else, or report progress at a high level.From its SKILL.md
npx -y skills add darrenbuse/Claudery --skill session-summaryAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
2.6 KB, as published. Nobody here has run it
Session Summary
Structure
Three top-level sections, in this order:
**Achieved**
- **Workstream name**
- Outcome with its artifact (PR #, commit, path, URL)
- Outcome
- **Another workstream**
- Outcome
**Open — needs you**
- Action only the user can take (merge, rotate, log in, decide)
**Open — future work**
- **Grouping where helpful**
- Known gap or natural next step nobody owns yet
Rules
- Group by workstream, not chronology. The reader wants what happened to each thread of work, not the order events occurred.
- Outcomes, not activities. "Built the parser skill" earns a bullet; "explored the codebase" does not — unless the finding was the deliverable, in which case state the finding.
- Every bullet carries its artifact. A merged change names its commit; an open change names its PR; a new file names its path. The summary is a map back to the work.
- Split the open items by owner. "Needs you" holds only actions the user must take themselves — merges, credentials, decisions. Everything else — known gaps, deferred fixes, natural next steps — is "future work". A reader scans "needs you" as a to-do list; mixing in backlog buries it.
- Be honest in the open sections. Skipped steps, failed attempts and discovered risks are outcomes of the session too. Name them plainly; the achieved list earns trust only if the open list is complete.
- Two levels maximum. Bold theme headers, one level of sub-bullets. If a theme needs a third level, it is two themes.
- Scale to the session. A short session may not need themed groupings or the future-work section; keep the achieved/needs-you split always.
Prose inside bullets follows the writing-style skill: specific, positive form, no filler.