skills.rest
AlexKapadia
AlexKapadiaCOMMUNITY
Explore all skills by this author →
GitHub

export-run-as-report

Package a Pixie run into a Markdown report with assets and provenance files.

6|1|Updated May 17, 2026
Search Tags:#markdown#reporting#provenance#sharing#export#artefacts#pixie
One-click install
npx skills add https://github.com/AlexKapadia/Pixie --skill export-run-as-report
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: export-run-as-report
Source: https://github.com/AlexKapadia/Pixie/tree/main/.claude/skills/export-run-as-report
Command: npx skills add https://github.com/AlexKapadia/Pixie --skill export-run-as-report

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Packages ONE Pixie run into a rendered, human-readable Markdown report with an assets/ folder and provenance files.

Core Features & Use Cases

  • Render a single Pixie run into a Markdown report (report.md) with an assets/ folder containing artefacts.
  • Include provenance data by packaging inputs.json and outputs.json alongside the report.
  • Provide a ready-to-share artifact bundle for audits, documentation, or collaboration.

Quick Start

Select a run and execute the export-run-as-report skill to generate the report bundle.

Frequently Asked Questions about export-run-as-report

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

FAQPage Schema
How do I export a Pixie run as a markdown report for audit sharing?▼

You can export a Pixie run as a markdown report by selecting the run and executing the export-run-as-report workflow, which generates a ZIP file containing report.md, inputs.json, outputs.json, and an assets folder.

What is included in the provenance files when exporting tool runs to markdown?▼

The provenance files included in the markdown report export are inputs.json and outputs.json, which are packaged alongside report.md inside a ZIP archive to provide a verifiable record of the tool run.

Can I generate a shareable artifact bundle with artefacts from a single run?▼

Yes, you can generate a shareable artifact bundle that packages a single run into a rendered markdown report with an assets folder containing artefacts, providing a ready-to-share record for documentation or collaboration.

How do I package tool run outputs and inputs for collaboration documentation?▼

You package tool run outputs and inputs for collaboration by rendering the run into a markdown report, which enforces routing decisions and outputs a ZIP containing the report, provenance data, assets, and a manifest file.

Does the markdown report export include a manifest file for the assets folder?▼

Yes, the markdown report export includes a manifest file within the output ZIP archive, ensuring the assets folder, report.md, and provenance files are properly organized and documented for audits.

Why does the report generation workflow read the KILL_FILE.md during export?▼

The report generation workflow reads the .build/KILL_FILE.md during export to enforce safety protocols and routing decisions before packaging the run into the final ZIP archive.

Related Skills

Explore More Content & Communication Skills→
AlexKapadiaAlexKapadia
6

export-run

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

Community
Intermediate
ImaginerLabsImaginerLabs

code-review-workflow

Audit code changes through four stages and generate a Markdown review report.

Official
Advanced
AlexKapadiaAlexKapadia
6

audit-disk-usage

Report disk usage across Pixie tool environments without modifying files.

Community
Advanced
saiteja007-mvsaiteja007-mv

graphify-windows

Transform raw file folders into knowledge graphs with HTML and JSON outputs.

Community
Advanced