agentleFS
Sign inStart free
diz5diz5/agentic-workflow-toolkit/.claude/skills/list-sessions/SKILL.md

list-sessions

Skill1 starsChanged 3 months agoMITView on GitHub

List past Claude Code sessions for the current project as a quick summary table — session ID, last-active time, transcript size, and name (the /rename custom title, else the auto-generated title). Use when the user wants to see, list, browse, or summarize related/past sessions for this project.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. gdaunlam/skills★ 1same name
    2. Takkuya/claude-skills★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository5 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run the helper script (it derives the project's session folder from the working directory):

    line 14
  2. Very specific:

    After showing the table, remind the user they can reopen one with /resume (in-session picker) or claude --resume from the terminal.

    line 47

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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 Sessions

Show a summary of all Claude Code sessions belonging to the current project so the user can quickly find and resume one.

How to run

Run the helper script (it derives the project's session folder from the working directory):

python3 .claude/skills/list-sessions/list_sessions.py

Then present its output. The script already prints a clean table with:

  • ID — short session id (first 8 chars; full id is the .jsonl filename)
  • Last active — file modified time
  • Size — transcript size
  • Name — user /rename title if set, else the auto-generated AI title, else a truncated first prompt
  • ↳ summary — an optional hand-curated one-liner shown under a session, if one exists

Rows are sorted newest-first; the current session (if detectable) is marked ▶.

Curated summaries (best of both worlds)

The live columns above are always regenerated from disk, so nothing goes stale. The optional summary line is read from session-helper/session-info.md — a small, hand-maintained table of | + backtick-quoted session id + | summary | rows. To add or edit a session's summary, edit that file directly (no script/regeneration needed).

This replaced the older session-helper/refresh-sessions.sh (which regenerated a full registry and had a hardcoded "current session" id, so it went stale). That script is retired; session-info.md is now just the curated-summary store this skill reads.

Notes

  • Sessions live in ~/.claude/projects/<encoded-cwd>/*.jsonl, where Claude Code encodes the project path by replacing every / and . with -.
  • To inspect a different project, pass its absolute path as an argument: python3 .claude/skills/list-sessions/list_sessions.py /some/other/project
  • This skill is read-only — it never modifies session files.
  • After showing the table, remind the user they can reopen one with /resume (in-session picker) or claude --resume from the terminal.

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