session-list
Skill2 starsChanged 26 days agoMITView on GitHub
Lists all Claude Code sessions for a project or globally, sorted by recency, size, or duration. Use when the user asks how many sessions they have, wants to see recent sessions, says "list sessions", or wants a session inventory.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- manastalukdar/ai-devstudiotheir own version, first seen Oct 13, 2026
- Svampen/claude-skillstheir own version, first seen Oct 11, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- manastalukdar/ai-devstudio★ 1same name
- Svampen/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 repository14 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- session-cleanupSkill
- session-deleteSkill
- session-detailSkill
- session-diffSkill
- session-exportSkill
- session-memory-auditSkill
- session-memory-searchSkill
- session-memorySkill
- session-resumeSkill
- session-searchSkill
- session-statsSkill
- session-tasksSkill
- session-timelineSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
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
- Very specific: line 38
If the user asks for more detail on a specific session, use /session-stats <session-id>.
≈ “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.
Files
Session List
List all sessions, optionally filtered by project and sorted.
Step 1: Run the listing script
bun run ${CLAUDE_PLUGIN_ROOT}/lib/session-store.ts list --limit 20 --format jsonTo filter by project:
bun run ${CLAUDE_PLUGIN_ROOT}/lib/session-store.ts list --project "<filter>" --limit 20 --format jsonTo sort by size or duration instead of recency:
bun run ${CLAUDE_PLUGIN_ROOT}/lib/session-store.ts list --sort size --limit 20 --format jsonStep 2: Present results
The script outputs a JSON array (each entry has a title: custom title if set, else auto title; may be null). Present as a markdown table:
| # | Session ID | Title | Project | Date | Messages | Duration | Size |
Highlight the current session if it matches the working directory. Show the resume command: claude --resume <session-id>.
If the user asks for more detail on a specific session, use /session-stats <session-id>.
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
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.