view-runs

Fetch and display recent runs of a named Pixie tool from pixie.db or the live API.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Lists recent runs of a single Pixie tool from pixie.db, including inputs, status, duration, and truncated outputs to help you quickly understand tool behavior.

Core Features & Use Cases

  • Retrieve the last runs for a named tool via the live API or local pixie.db fallback.
  • Render results as a markdown table with When, Duration, Status, Inputs (masked), and Error for easy scanning.
  • Use case: quickly answer questions like "What happened in the last run of tool X?" and compare runs for debugging.

Quick Start

Ask Pixie for the last runs of a specific tool and it will display a concise run history table.

Frequently Asked Questions about view-runs

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

FAQPage Schema
How do I view recent runs of a specific tool to diagnose failures?

To view recent tool runs, you can query pixie.db or the live API to retrieve a history table displaying when the run occurred, its duration, status, masked inputs, and any errors for quick diagnostics.

What details are included when reviewing past tool run history?

Past tool run history includes a rendered table with the timestamp, duration, status, masked inputs, and truncated error outputs to help you quickly understand tool behavior and compare runs for debugging.

Can I retrieve tool run history locally if the live API is unavailable?

Yes, you can retrieve tool runs using a local pixie.db fallback if the live API is unavailable, ensuring you can still access recent run history, status, and inputs for diagnostics.

How do I verify the inputs used in a previous tool run?

You can verify previous tool inputs by viewing the run history table, which displays masked inputs alongside the run status and duration to help you confirm what parameters were passed.

What is the best way to compare recent tool runs for debugging?

The best way to compare runs for debugging is to fetch the recent run history for a specific tool, which renders a concise table allowing you to scan statuses, durations, and errors side-by-side.