Install a Pixie tool from a ZIP by unpacking under tools/ and validating with uv sync.
npx skills add https://github.com/AlexKapadia/Pixie --skill import-tool
Please help me install this Agent Skill. Skill: import-tool Source: https://github.com/AlexKapadia/Pixie/tree/main/.claude/skills/import-tool Command: npx skills add https://github.com/AlexKapadia/Pixie --skill import-tool
This Skill enables teams to quickly import and set up Pixie tools that have been packaged as ZIP archives, ensuring consistent deployment in the local Pixie environment.
Install a shared Pixie tool from a ZIP by unpacking it under tools/ and then running uv sync to validate.
High-intent search queries and answers about installing and using this skill.
To install a shared Pixie tool, unpack the ZIP archive into the tools/ directory and run uv sync to validate its structure, dependencies, and readiness for dashboard use.
Validation enforces security checks, mandates exactly one top-level folder named after the tool_id, and confirms essential files like tool.json, pyproject.toml, and main.py are present.
Yes, the ZIP must contain exactly one top-level folder named after the tool_id. This folder must include essential files like tool.json, pyproject.toml, and main.py to pass validation.
Validation fails if the ZIP structure lacks exactly one top-level folder named after the tool_id, misses essential files like tool.json, pyproject.toml, or main.py, or triggers security checks.
Yes, importing a packaged Pixie tool from a ZIP restores tool configurations across machines by unpacking under tools/ and running uv sync with the Pixie validator to ensure readiness.
jacobcyArchive completed OpenSpec changes with artifact status checks and spec synchronization.
AlexKapadiaDiagnoses Pixie installation health across server, database, ports, dashboard, venv, Python, and uv versions.
AlexKapadiaPackage a Pixie tool's source code folder into a zip, excluding sensitive files.
leeoveryApply pending migrations to sync workflow files with system design.
