agentleFS
Sign inStart free
JewgahJewgah/claude-code-skills/skills/sessions/SKILL.md

sessions

Skill2 starsChanged 3 months agoMITView on GitHub

List recent Claude Code sessions across all projects with project name, session ID, resume command, and short description of what the session was about. Handles multiple parallel sessions per project. Use when the user wants to find, resume, or recall a previous Claude conversation — especially before/after a reboot.

24 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use tool-rename-deprecation, add-policy and 10 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.
  • gitpod-ioSkill

    tool-rename-deprecation

    Ensure renamed built-in tool references preserve backward compatibility. Use when renaming a toolReferenceName, tool set referenceName, or any tool identifier. Run on ANY change to tool registration code. Covers legacyToolReferenceFullNames for tools and legacyFullNames for tool sets.

    Also in 5 projects that use this

  • OpenCortexIDESkill

    add-policy

    Use when adding, modifying, or reviewing VS Code configuration policies. Covers the full policy lifecycle from registration to export to platform-specific artifacts. Run on ANY change that adds a `policy:` field to a configuration property.

    Also in 4 projects that use this

  • gitpod-ioSkill

    agent-sessions-layout

    Agent Sessions workbench layout — covers the fixed layout structure, grid configuration, part visibility, editor modal, titlebar, sidebar footer, and implementation requirements. Use when implementing features or fixing issues in the Agent Sessions workbench layout.

    Also in 3 projects that use this

  • slopusSkill

    metrics-graphana

    Query and manage Grafana dashboards and Prometheus metrics for Happy infrastructure. Covers grafanactl CLI usage, direct Prometheus queries through Grafana proxy, and dashboard-as-code workflows. Use when user asks about metrics, dashboards, monitoring, Grafana, Prometheus, or wants to add/modify panels.

    Also in 3 projects that use this

  • slopusSkill

    control-flow

    Analyze and design control flows and data structures. Produces compact ASCII tree diagrams showing triggers, call chains, payload shapes, state mutations, and re-render effects. Use when user asks to diagram, trace, visualize, or design a flow or data structure.

    Also in 3 projects that use this

  • TheKREATORSSkill

    refactor-clean

    No description

    Also in 3 projects that use this

  • +2 more from gitpod-io

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 21 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When invoked, run the helper script and pass its output through.

    line 8
  2. Very specific:

    Default mode prints one flat chronological list — [timestamp] project session-id + the first prompt — with the resume hint once at the …

    line 25
  3. Distinctive:

    If the user names a specific topic or project, point out the matching session(s) at the top.

    line 31
  4. Distinctive:

    If there are many sessions for one project, note it ("3 parallel sessions for X today") so the user knows multiple threads exist.

    line 32
  5. Very specific:

    If the user is about to reboot, remind them: claude --resume <session-id> restores full context.

    line 33

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

List recent Claude Code sessions

When invoked, run the helper script and pass its output through.

Step 1 — pick the mode from the skill argument

ArgumentCommandView
(none) or recentpython3 ~/.claude/skills/sessions/list_sessions.pydefault — one flat list, newest first, across all projects
project (or "grouped", "by project")python3 ~/.claude/skills/sessions/list_sessions.py --groupedgrouped per project, so parallel sessions are visible

Other arguments (use only if the user asks):

  • --days 30 — widen the window to 30 days (default 7)
  • --all — show everything ever recorded
  • --project <substring> — filter by project name, case-insensitive (e.g. --project myapp). Unrelated to the project grouping mode above; combines with both views.

Step 2 — present the output

Default mode prints one flat chronological list — [timestamp] project session-id + the first prompt — with the resume hint once at the bottom.

--grouped mode prints: project header → cd line → one block per session with timestamp, session UUID, first user prompt, and the exact claude --resume <id> command.

After running it:

  • Pass through the output as-is — do not re-summarise every session, the user wants the raw list.
  • If the user names a specific topic or project, point out the matching session(s) at the top.
  • If there are many sessions for one project, note it ("3 parallel sessions for X today") so the user knows multiple threads exist.
  • If the user is about to reboot, remind them: claude --resume <session-id> restores full context; claude --resume alone opens an interactive picker scoped to the current working directory, so they must cd into the project first if they use the picker form.

Notes on the data

  • Sessions live in ~/.claude/projects/<encoded-cwd>/<session-uuid>.jsonl.
  • One .jsonl = one session. Multiple files in the same project dir = parallel sessions.
  • The script extracts the first real user prompt as the "description" — it skips system/caveat blocks.
  • Image-only prompts show as [Image #1]; that's expected, not a bug.
  • The encoded directory name (-Users-you-projects-myapp) isn't always the same as the real cwd; the script reads the cwd field from inside the JSONL for accuracy.

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