label-run

Label a Pixie run and protect its artefacts from auto-prune.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill lets you assign a short human-memorable label to a specific Pixie run, making it easy to find and protecting its outputs from auto-pruning.

Core Features & Use Cases

  • Assigns run.label in Pixie to enable quick search with find-output and listing.
  • Protects labelled runs from auto-prune, ensuring artefacts remain accessible.
  • Supports usage when users need to name, annotate, or reference a particular run (without renaming tools).

Quick Start

Label a Pixie run with a descriptive tag and protect its artefacts from auto-prune.

Frequently Asked Questions about label-run

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

FAQPage Schema
How do I label a Pixie run to protect artifacts from auto-prune?

To label a Pixie run, the Skill resolves the run_id, validates a descriptive label string, and applies a patch to set the run label, which automatically protects its artifacts from auto-prune deletion.

Can I search for specific Pixie runs using a custom label?

Yes, assigning a descriptive label to a Pixie run enables quick search and retrieval using find-output and listing commands, making it easy to locate specific runs across tools and sessions.

How do I prevent important Pixie run outputs from being deleted by auto-prune?

You can protect Pixie run outputs from auto-prune by assigning a descriptive label to that run, ensuring its artifacts remain accessible and are not automatically deleted.

Does labeling a Pixie run modify the associated tools or other runs?

No, applying a label to a Pixie run only patches the specific run to set a named reference. It ensures no changes are made to the associated tools or any other runs.

What is the best way to annotate a Pixie run for easier retrieval across sessions?

The best way to annotate a Pixie run is to assign a short, human-memorable label that acts as a named reference, allowing you to easily identify, categorize, and persist the run for retrieval across sessions.

What do I need before I can apply a label to a Pixie run?

Before labeling a Pixie run, you need the specific run_id to target and a valid label string to assign, which the Skill validates before applying the patch to protect the artifacts.