skills.rest
SpecterShell
SpecterShellCOMMUNITY
Explore all skills by this author →
GitHub

axec-list

List tracked axec sessions with status, UUID, name, and command metadata.

Updated Mar 20, 2026
Search Tags:#monitoring#cli#sessions#list#process-management#axec
One-click install
npx skills add https://github.com/SpecterShell/axec --skill axec-list
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: axec-list
Source: https://github.com/SpecterShell/axec/tree/main/skills/axec-list
Command: npx skills add https://github.com/SpecterShell/axec --skill axec-list

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Managing and tracking multiple axec sessions is error-prone without a quick overview of active and past sessions.

Core Features & Use Cases

  • List sessions with UUID, name, status, timestamps, and the command used.
  • Optionally output metadata in JSON via --json for programmatic consumption.
  • Quickly identify and inspect the backend type (pty, pipe, or auto) for each session.

Quick Start

Run axec list to see all current sessions and their statuses, using --json for structured output when programmatic access is required.

Frequently Asked Questions about axec-list

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

FAQPage Schema
How do I list all active process management sessions and inspect their status?▼

To list active process management sessions and inspect their status, run axec list to view UUID, name, status, PID, command, timestamps, and backend type for all tracked sessions.

Can I get JSON output for axec sessions to use in programmatic monitoring scripts?▼

Yes, you can get JSON output for axec sessions by running axec list with the --json flag, which returns structured metadata including UUID, name, status, PID, command, and backend details for programmatic consumption.

What details are displayed when tracking multiple CLI sessions at a glance?▼

Tracking multiple CLI sessions displays the UUID, name, status, PID, command, started at, exited at timestamps, and backend type (pty, pipe, or auto) for each session.

How do I identify the backend type of a running session during process management?▼

To identify the backend type of a running session during process management, list the sessions to inspect each session's metadata, which explicitly reports whether the backend is pty, pipe, or auto.

Why does monitoring multiple sessions become error-prone without a list overview?▼

Monitoring multiple sessions becomes error-prone without a list overview because tracking individual UUIDs, statuses, and commands manually increases the risk of misidentifying active versus exited sessions.

Does axec-list require any external dependencies to inspect session states?▼

No, axec-list does not require any external dependencies to inspect session states, as it directly queries tracked session metadata to report status, PID, and backend information.

Related Skills

Explore More Software Engineering Skills→
SpecterShellSpecterShell

axec-kill

Terminate axec sessions by name, UUID, or all with JSON output.

Community
Intermediate
Nickalus12Nickalus12
2

status

Read and report active Loom session metadata without mutation.

Community
Intermediate
SpecterShellSpecterShell

axrepl-kill

Terminate axrepl REPL sessions by name, UUID, or all via CLI.

Community
Basic
L3DigitalNetL3DigitalNet
6

strace

Trace system calls and signals of a process to diagnose OS-level issues.

Official
Intermediate