axrepl-list

List REPL sessions with UUID, name, driver, status, and command.

Updated Mar 20, 2026
One-click install
npx skills add https://github.com/SpecterShell/axec --skill axrepl-list
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: axrepl-list
Source: https://github.com/SpecterShell/axec/tree/main/skills/axrepl-list
Command: npx skills add https://github.com/SpecterShell/axec --skill axrepl-list

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables you to quickly inventory and monitor all tracked REPL sessions by listing their UUIDs, names, drivers, statuses, and commands, reducing context switching during debugging and orchestration.

Core Features & Use Cases

  • List all tracked REPL sessions with UUID, name, driver, status, and command.
  • Filter out non-REPL axec sessions by focusing on recognized REPL drivers (python, node, bash, zsh, etc.).
  • Use in workflows to audit, monitor, or troubleshoot multiple REPL sessions across a running daemon.

Quick Start

Run axrepl list to display all known REPL sessions and their statuses.

Frequently Asked Questions about axrepl-list

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

FAQPage Schema
How do I list all active REPL sessions and their current status?

List all tracked REPL sessions by running the list command to display UUID, name, driver, status, and command. This provides structured metadata to monitor sessions across running daemons for auditing and troubleshooting.

What information is included when monitoring REPL sessions?

Monitoring REPL sessions provides structured metadata including UUID, name, driver, status, and command. This allows you to audit and troubleshoot multiple sessions across axrepl deployments without context switching.

Can I get REPL session data in JSON format for programmatic consumption?

Yes, the skill supports JSON output for programmatic consumption. This allows workflows and scripts to parse UUIDs, names, drivers, statuses, and commands automatically for orchestration and monitoring.

Does the REPL session list filter out non-REPL axec sessions?

Yes, the session list filters out non-REPL axec sessions by focusing only on recognized REPL drivers such as python, node, bash, and zsh. This ensures the inventory displays only valid interactive session data.

Why do I need to inventory REPL sessions during debugging?

Inventorying REPL sessions during debugging reduces context switching by providing a quick overview of all UUIDs, drivers, and statuses. This helps you identify and target specific active or idle sessions for troubleshooting.