export-run

Package a Pixie run into a ZIP with inputs, outputs, artefacts, and report.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Exporting a Pixie run as a complete, self-contained archive is often needed for sharing, archiving, or troubleshooting. This Skill packages inputs.json, outputs.json, artefacts, and a generated report into a single ZIP, preserving provenance and structure.

Core Features & Use Cases

  • Packages one run's raw data: inputs.json, outputs.json, artefacts/, and a report (report.md) into one ZIP.
  • Keeps file integrity with a consistent layout suitable for archival or transfer.
  • Use Case: when you need to hand off a run to a teammate or attach it to a ticket for reproducibility.

Quick Start

Export the currently selected Pixie run as a ZIP archive.

Frequently Asked Questions about export-run

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

FAQPage Schema
How do I export a Pixie run as a ZIP archive for sharing?

To export a Pixie run as a ZIP archive, this Skill packages inputs.json, outputs.json, all artefacts, and a generated report into a single portable file while preserving the original directory layout and provenance for easy sharing.

What files are included when I package a single run into a ZIP?

Packaging a single run into a ZIP includes inputs.json, outputs.json, a generated report (report.md), and all artefacts organized under the artefacts/<tool>/<run>/ directory structure to maintain file integrity.

Does exporting a Pixie run modify the original source data?

Exporting a Pixie run operates strictly read-only, meaning it preserves artefacts and excludes rendering changes or any modifications to the original source data during the archival process.

Can I use this ZIP export for troubleshooting and archiving purposes?

Yes, the ZIP export is explicitly suitable for archiving, troubleshooting, and handing off a run to a teammate or attaching it to a ticket for reproducibility while maintaining a consistent directory layout.

What is the best way to preserve provenance when archiving a run?

The best way to preserve provenance when archiving a run is to package it into a self-contained raw ZIP that maintains the original directory layout, inputs, outputs, and all associated artefacts without applying rendering changes.

Are there limitations to what is included in the run export ZIP?

The main limitation of the run export ZIP is that it excludes rendering changes and excludes any modification to source data, operating strictly read-only to package only the raw run data and generated report.