copy-output-to

Copy a single Pixie artefact file to a user-specified filesystem path.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Copy a single artefact file to a user-specified path, ensuring a byte-for-byte copy without altering the source.

Core Features & Use Cases

  • Copy exactly one artefact from artefacts/<tool>/<run>/<file> to a user-specified destination while preserving metadata.
  • Guard against overwrites by requiring explicit --force and validating destination paths.
  • Integrates safely within Pixie's offline environment without modifying source artefacts.

Quick Start

Specify the artefact and destination with --to and run the skill to copy the file.

Frequently Asked Questions about copy-output-to

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

FAQPage Schema
How do I copy a Pixie artefact to a local disk path?

To copy a Pixie artefact to disk, specify the source file from the artefacts index and a valid filesystem destination path using the --to parameter for a byte-for-byte copy.

Can I overwrite an existing file when copying an artefact to disk?

Overwriting an existing file when copying an artefact requires the explicit --force flag, guarding against accidental data loss during artifact archival.

Does copying a Pixie artefact modify the original source file?

Copying a Pixie artefact creates a byte-for-byte copy without modifying the source, ensuring safe post-run data handling within the offline environment.

What is the best way to archive a single artefact from a specific tool run?

The best way to archive a single artefact from a specific tool run is to copy the file from the artefacts index to a user-specified destination, preserving its metadata.

Why does the artefact copy operation require a valid destination path?

The artefact copy operation requires a valid destination path to safely locate the source from the artefacts index and write the file to the correct disk location.