list-sessions

Parse SAGA dashboard JSON to list active sessions with uptime.

13|1|Updated Nov 21, 2025
One-click install
npx skills add https://github.com/Roeia1/SAGA --skill list-sessions
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: list-sessions
Source: https://github.com/Roeia1/SAGA/tree/main/plugin/skills/list-sessions
Command: npx skills add https://github.com/Roeia1/SAGA --skill list-sessions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

List all currently running SAGA sessions and present their status in a structured, easy-to-scan format to simplify monitoring and orchestration.

Core Features & Use Cases

  • Parses the raw JSON output from the Saga dashboard to extract session name, status, and output location.
  • Computes approximate uptime for each session from its timestamp and displays it in a human-friendly format.
  • Exposes safe, discoverable commands to stream logs or terminate a session for quick incident response.
  • Use Case: A developer or operator wants to quickly see which stories are active and take action if a session is stuck.

Quick Start

Run the list sessions command in the Saga dashboard to display all active sessions.

Frequently Asked Questions about list-sessions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I monitor active Saga sessions and check their uptime?

You can monitor active Saga sessions by parsing the raw JSON output from the Saga dashboard to extract session names, statuses, and output locations, while computing approximate uptime from timestamps for quick review.

What is the best way to view all running Saga sessions for quick incident response?

The best way to view running Saga sessions is by reading the JSON output, validating fields, and presenting structured results to help you quickly see which stories are active and take action if a session is stuck.

How do I stream logs or terminate a stuck session in the Saga dashboard?

You can stream logs or terminate a stuck session in the Saga dashboard by using safe, discoverable commands exposed after parsing the raw session output to ensure deterministic behavior and auditable incident response.

Does the Saga session monitor work with raw JSON output?

Yes, the Saga session monitor works with raw JSON output by parsing the data, validating specific fields, and enforcing deterministic behavior to safely expose auditable commands for ongoing work orchestration.

When do I need to parse Saga session output for monitoring?

You need to parse Saga session output for monitoring when you are a developer or operator wanting to quickly see which stories are active, review structured statuses, and take action if a session is stuck.

Why does my Saga session monitoring require field validation?

Saga session monitoring requires field validation to enforce deterministic behavior by reading the JSON output accurately, ensuring that safe, auditable commands are exposed for streaming logs or terminating sessions.