view-logs

Tail live stderr and stdout logs from Pixie tools.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Tail live logs from Pixie tools to diagnose silent failures and startup issues.

Core Features & Use Cases

  • Tails live stderr and stdout from a currently running tool, exposing a real-time view for debugging.
  • Reads recent logs from previous runs when a tool isn't active to troubleshoot reproducible errors.
  • Integrates with the Pixie web dashboard to quickly identify which tool to inspect and to switch between live logs and run histories.

Quick Start

Open the Pixie dashboard, pick a tool, and view its live or recent logs to start diagnosing issues.

Frequently Asked Questions about view-logs

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

FAQPage Schema
How do I tail live logs from a running tool to debug silent failures?

Tail live logs by accessing the logs endpoint at /api/tools/{tool_id}/logs to stream real-time stderr and stdout output from a currently running tool to diagnose silent failures and startup issues.

Can I view recent stdout and stderr logs from previous runs when a tool isn't running?

Yes, you can read recent logs from previous runs when a tool isn't active to troubleshoot reproducible errors. The tool handles NOT_RUNNING states and renders previous output in a plain block with clear headers.

What is the best way to inspect tool output in the Pixie dashboard without affecting running processes?

The best way to inspect tool output without affecting running processes is to use the Pixie dashboard to pick a tool and view its live or recent logs, exposing a real-time view for debugging across dashboard tools.

Why does my tool log stream show a PIXIE_UNREACHABLE error state?

A PIXIE_UNREACHABLE error state appears when the logs endpoint at /api/tools/{tool_id}/logs cannot connect to the target tool. The Skill handles this state explicitly alongside NOT_RUNNING states during log rendering.

Do I need a specific logs endpoint to read stderr and stdout from Pixie tools?

Yes, you need access to the logs endpoint at /api/tools/{tool_id}/logs to read stderr and stdout. This endpoint allows you to tail live logs from currently running tools and read recent logs from previous runs.