rename-tool

Name: rename-tool
Availability: InStock
Author: alexkapadia

Rename a Pixie tool by updating its id, folder, and tool.json references.

6|1|Updated May 17, 2026

Search Tags:#validation #repository #rename #filesystem #tool-management #pixie #tool-json

Ready to run

npx skills add https://github.com/AlexKapadia/Pixie --skill rename-tool

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: rename-tool
Source: https://github.com/AlexKapadia/Pixie/tree/main/.claude/skills/rename-tool
Command: npx skills add https://github.com/AlexKapadia/Pixie --skill rename-tool

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Renaming a Pixie tool often creates broken references, misaligned IDs, and outdated tool metadata. This skill provides a safe, auditable flow to rename a tool's id, folder name, and related references across the repository and validation layer.

Core Features & Use Cases

Identify the source tool and the new ID; verify existence and uniqueness.
Stop the tool if it is currently running to prevent runtime conflicts.
Rename the folder on disk and update the tool.json id to preserve display name and metadata.
Rewrite historical references in pixie.db for runs, state, and validation to avoid broken links.
Run the validator to ensure the rename is consistent with the repository structure.

Quick Start

Provide the old_id and new_id when prompted to initiate the rename flow.

Frequently Asked Questions about rename-tool

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

FAQPage Schema

How do I safely rename a Pixie tool across a repository?▼

To safely rename a Pixie tool, you update its id, folder name, and tool.json file. The process includes preflight checks, stopping running tools, rewriting pixie.db references, and validating the repository structure.

What happens to pixie.db references when I change a tool's id?▼

When changing a tool's id, historical references in pixie.db for runs, state, and validation are rewritten. This prevents broken links and ensures runtime state remains connected to the newly renamed tool.

When do I need to update tool.json during a repository rename?▼

You need to update tool.json during a repository rename to preserve the display name and metadata. This aligns the tool's internal id with its new folder name on disk and maintains configuration consistency.

Why should I stop a running tool before renaming its folder on disk?▼

You should stop a running tool before renaming its folder to prevent runtime conflicts. Stopping the tool ensures the filesystem and pixie.db can be updated without corrupting active state or breaking validation.

How do I validate a tool slug change after migrating files?▼

You validate a tool slug change by running the built-in validator after rewriting folder names and database references. This ensures the new id and tool.json metadata are consistent with the repository structure.

Can I fix naming conflicts by migrating tool ids in a Pixie repository?▼

Yes, you can fix naming conflicts by migrating tool ids in a Pixie repository. The rename process verifies uniqueness during preflight checks and updates the filesystem and tool.json to resolve the conflict safely.