Skill Recap

Look back over one or more sessions and work out how the agent and its sub-agents used their skills: where a skill helped the work, and where a skill, or a missing one, cost the session. End the recap with findings, each backed by evidence from the transcripts, and a verdict.

Parameters

• <skills-repo>: the user's own skills repo on GitHub, as owner/repo.

1. Select the sessions

• By default, cover the current session and every sub-agent it spawned, at any depth. The session itself is in your context. Sub-agents ran in their own contexts, so read their transcripts from disk.
  • When part of the session was compacted away: read its transcript for the missing stretch.
• When the user names a scope such as a time window, a project or a list of sessions, use exactly that scope, sub-agents included.
  • When the scope can be read more than one way, such as which projects a time window covers: ask before reading.

Where transcripts live

Claude Code keeps transcripts as files with one JSON object per line, laid out as below. The layout can change between versions, so when a path doesn't resolve, search ~/.claude/projects/ for the session id.