Cheatsheet

Open Claude Code in the Pixie repo, then type any of these.

Add a tool

Add a Pixie tool that <does the thing>

Add github.com/<user>/<repo> as a Pixie tool

Wrap ./scripts/<file>.py as a Pixie tool

Convert ./<notebook>.ipynb to a Pixie tool

Wrap ffmpeg as a Pixie tool

Import ./shared/<tool>.zip

Edit / maintain

Update the foo tool: add a slider for X from 0 to 100

Rename foo to bar

Duplicate the foo tool as foo-v2

Archive foo (I'll bring it back later)

Remove the foo tool permanently

Lint the foo tool

Migrate the foo tool to the latest schema

Re-validate every tool

Secrets & data

Set the ANTHROPIC_API_KEY for the rag-with-citations tool

Fetch https://example.com/data.csv into the foo tool

Fetch the kaggle.com/datasets/foo/bar into the baz tool

Import ~/Downloads/iris.csv into the foo tool

Runs & outputs

Show me the last 5 runs of the foo tool

Find PNG outputs from this week

Label the last run of foo "final-budget"

Star run abc123

Export run abc123 to ./exports

Export run abc123 as a markdown report

Export this output as SVG

Bulk-export all starred runs from the lorenz tool

Copy this output to ~/Documents/results.csv

Copy this text to the clipboard

Open the artefacts folder for foo in Explorer

Clear runs older than 30 days from foo

Workspaces & tags

Create a "Finance" workspace

Add black-scholes-greeks to the Finance workspace

Tag foo as 'nlp' and 'production'

Cite arxiv.org/abs/2106.09685 on the foo tool

Share

Package the foo tool as a zip

Set up "reports" as an export target pointing at ~/Documents/Reports

Debug

Why is the foo tool failing validation?

Show me the stderr for foo

Run pixie doctor

Is Pixie running?

List all tools

Validate foo against its reference fixtures

---

If the routing picks a different skill from what you wanted, just say so — e.g. “no, use update-tool not debug-tool” — and Claude Code will correct course.