find-output

Locate saved Pixie artefacts by substring matching against filename, label, or tags.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Locate saved Pixie artefacts by substring against filename, label, or tags across all tools. You use this when the user requests to find, search, look for, locate, or grep a saved output, artefact, or file. Do NOT use to list everything (list-outputs), one tool's runs (view-runs), or open artefacts folders (open-artefacts-folder).

Core Features & Use Cases

  • Search across the artefact index by a text substring to identify matching artefacts based on filename, label, or any tag.
  • Filter results across tools and runs to quickly surface relevant outputs.
  • Use cases include locating a specific artefact containing a keyword, auditing outputs, or gathering evidence of tool results.

Quick Start

Enter a search substring to locate matching artefacts across the index.

Frequently Asked Questions about find-output

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

FAQPage Schema
How do I search for saved Pixie outputs by a text substring?

To search for saved Pixie outputs, enter a text substring to match against artefact filenames, labels, or tags. This queries the read-only artefact index across all tools and returns matching outputs without modifying any files.

Can I filter saved artefacts across multiple tools using a keyword?

Yes, you can filter saved artefacts across multiple tools by providing a keyword substring. The search matches the keyword against filename, label, or tag metadata to quickly surface relevant outputs from the artefact index.

What is the best way to find historical tool runs containing a specific tag?

The best way to find historical tool runs containing a specific tag is to search the artefact index using that tag as a substring. This read-only query matches tags and labels to locate the exact output without modifying artefacts.

Does searching for artefacts by substring modify the original files?

Searching for artefacts by substring does not modify the original files. The search enforces read-only querying against the artefact index, ensuring safe, non-destructive behavior when locating outputs by filename, label, or tags.

When should I use a substring search instead of listing all outputs?

You should use a substring search when you need to locate a specific artefact containing a keyword, rather than listing every saved output. It filters results across tools and runs to quickly surface matching files by filename, label, or tags.