Stats
Actions
Tags
From saga-core
Lists running SAGA sessions in a table with story ID, elapsed start time, session name, plus commands to stream logs or kill sessions.
How this skill is triggered — by the user, by Claude, or both
Slash command
/saga-core:list-sessionsThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
!`npx @saga-ai/dashboard sessions list`
!npx @saga-ai/dashboard sessions list
The command above outputs a JSON array of session objects:
[
{
"name": "saga-story-my-story-id-1704067200000",
"status": "running",
"outputFile": "/tmp/saga-sessions/saga-story-my-story-id-1704067200000.out"
}
]
If the array is empty, report:
No SAGA sessions are currently running.
If sessions exist, parse each session name to extract:
Present in a table format:
## Running Sessions
| Story | Started | Session Name |
|-------|---------|--------------|
| login-flow | 2h 30m ago | saga-story-login-flow-1704067200000 |
To stream logs: `saga sessions logs <session-name>`
To kill session: `saga sessions kill <session-name>`
The session name format is: saga-story-<storyId>-<timestamp>
To extract components:
saga-story- prefix-) are the timestamp (Unix milliseconds)storyIdExample: saga-story-auth-login-flow-1704067200000
saga-story- → auth-login-flow-1704067200000- → timestamp 1704067200000auth-login-flownpx claudepluginhub roeia1/saga --plugin coreLocates, lists, filters, and extracts structured data from Claude Code native session logs. Supports both single and multiple session analysis.
Guides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.