pixie-status

Report Pixie runtime uptime, warm tools, ports, and recent activity.

6|1|Updated May 17, 2026
One-click install
npx skills add https://github.com/AlexKapadia/Pixie --skill pixie-status
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pixie-status
Source: https://github.com/AlexKapadia/Pixie/tree/main/.claude/skills/pixie-status
Command: npx skills add https://github.com/AlexKapadia/Pixie --skill pixie-status

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pixie status provides a quick, read-only snapshot of the Pixie server, including whether the server is up, which tools are warm, active ports, and recent activity, to help users diagnose state issues without affecting the environment.

Core Features & Use Cases

  • Live runtime snapshot: uptime, warm tools, listening ports, and recent activity.
  • Quick diagnosis: determine if Pixie is running and which tools are currently active.
  • Safety-first: read-only status checks that avoid triggering any state changes.

Quick Start

Ask for Pixie status to see uptime, warm tools, and active ports.

Frequently Asked Questions about pixie-status

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

FAQPage Schema
How do I check if the Pixie server is currently running?

To check if the Pixie server is running, request a live runtime snapshot that reports uptime and active subprocess PIDs. This read-only status check confirms server availability without modifying any state.

What is the best way to monitor active tool subprocesses and ports in Pixie?

Monitoring active tool subprocesses and ports in Pixie is done by generating a read-only runtime status report. This snapshot lists warm tools, their corresponding PIDs, and listening ports for quick diagnosis.

How can I view recent runtime activity for Pixie without changing state?

You can view recent Pixie runtime activity without changing state by requesting a safety-first status check. This returns a read-only report containing a brief summary of recent activity alongside uptime data.

Does checking Pixie runtime status modify the server environment?

Checking Pixie runtime status does not modify the server environment. The status check is completely read-only, providing a safe snapshot of uptime, warm tools, and ports without triggering any state changes.

Why do I need a runtime snapshot to diagnose Pixie state issues?

A runtime snapshot is needed to diagnose Pixie state issues because it captures essential live data like uptime, warm tools, and active ports. This information isolates problems quickly without altering the environment.

Can I see which tools are warm in Pixie for quick debugging?

You can see which tools are warm in Pixie for quick debugging by requesting a status report. The read-only snapshot explicitly lists all warm tools, subprocess PIDs, and active ports for diagnosis.