list-outputs

List saved artefacts from Pixie tool runs in a read-only table.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Lists saved artefacts from Pixie tool runs, enabling quick discovery and retrieval of outputs such as files, images, transcripts, and logs without manually inspecting each run.

Core Features & Use Cases

  • Scan and display artefact metadata across one or more tools.
  • Filter results by tool, run, or output type and view details in a compact table.
  • Use case: quickly locate a saved transcript or a generated dataset from a prior run.

Quick Start

List artefacts across tools with a single request and preview the most recent outputs.

Frequently Asked Questions about list-outputs

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

FAQPage Schema
How do I find saved outputs and artefacts from previous tool runs?

To find saved outputs and artefacts from previous tool runs, you can browse a read-only view of metadata from the artefacts database and on-disk files to quickly locate saved files, images, or transcripts.

Can I filter saved artefacts by a specific tool or run?

Yes, you can filter saved artefacts by a specific tool, run, or output type. The results display in a compact table so you can quickly preview the most recent outputs.

What types of files and outputs can I browse from Pixie tool runs?

You can browse files, images, transcripts, and logs saved as artefacts from Pixie tool runs. The read-only view scans metadata across one or more tools without modifying the original data.

Does listing saved artefacts modify or alter the original output files?

No, listing saved artefacts is strictly read-only. It reads artefact metadata from the database and on-disk files to help you locate outputs quickly without modifying any underlying data.

What is the best way to browse generated datasets from prior runs across multiple tools?

The best way to browse generated datasets from prior runs is to scan artefact metadata across multiple tools at once, previewing the most recent outputs in a single compact table view.

Why manually inspect each run when looking for a specific saved transcript?

Manually inspecting each run is unnecessary when you can list saved artefacts across one or more tools. This approach reads metadata directly to help you locate a specific saved transcript quickly.