update-tool

Modify an existing Pixie tool's inputs, outputs, or dependencies and re-run the validator.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Modifies an existing Pixie tool's inputs, outputs, behaviour, dependencies, or metadata, then re-validates. Use when the user asks to change, edit, tweak, or add/remove an input/output. Do NOT use to rename (rename-tool), delete (remove-tool), fix broken (debug-tool), set a secret (set-secret), migrate format (migrate-tool-format), tag (tag-tool), or restructure files (organise-tool).

Core Features & Use Cases

  • Update a tool's configuration and/or code, then run a full validator to ensure compatibility with Pixie's workflow.
  • Ensure changes are safe by routing through the standard pre-flight checks, kill-file guidelines, and validator handoff.
  • Use case: When a user needs to adjust an input schema or add a new dependency and wants the updated tool to remain valid and runnable.

Quick Start

Update an existing tool's inputs and re-validate, ensuring the tool passes all checks.

Frequently Asked Questions about update-tool

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

FAQPage Schema
How do I update a Pixie tool's inputs and re-validate it?

To update a Pixie tool, modify the desired inputs, outputs, dependencies, or metadata in the tool directory, then run the validator to check affected files like tool.json, main.py, and pyproject.toml for pass, warn, or fail status.

What is the best way to add a new dependency to an existing tool?

Adding a new dependency requires updating the tool configuration and then running a full validator to ensure compatibility with Pixie's workflow, checking all affected files end-to-end to confirm the updated tool remains valid and runnable.

Can I use this to rename or delete a tool?

No, this is specifically for modifying an existing tool's inputs, outputs, behavior, or metadata. Use rename-tool for renaming, remove-tool for deletion, debug-tool for fixing broken tools, and migrate-tool-format for format migration.

How does the validator check affected files after a tool update?

The validator checks all affected files including tool.json, main.py, and pyproject.toml end-to-end, reporting a pass, warn, or fail status that guides the next steps to ensure changes are safe and compatible.

When do I need to re-validate after updating tool metadata?

You need to re-validate whenever you tweak a tool's inputs, outputs, dependencies, or metadata to ensure changes route through standard pre-flight checks and kill-file guidelines, keeping the tool valid and runnable.

Why does updating pyproject.toml for a tool require validation?

Updating pyproject.toml requires validation because the validator checks this file end-to-end alongside main.py and tool.json to ensure the updated dependencies and configuration remain compatible with Pixie's workflow.