custom_tool_builder_guide

To convert a GitHub repository into a reusable custom tool, initiate the process by providing the repo URL or local folder path to start drafting the tool. This guides you through cloning, refining, testing, and enabling the tool for chat workflows.

The custom tool building lifecycle involves standardized stages: start, refine, test, create, enable, promote, and delete. Each stage includes guided safety checks and requires explicit user approvals and clear command reviews before proceeding.

You can turn a local folder into a chat workflow custom tool without needing a remote git repo. The tool builder accepts both local folder paths and remote repository URLs to initiate the drafting and creation process.

The best way to test custom tools is by using the built-in lifecycle validation step. After drafting and refining your tool from a repository, the testing stage applies safety checks to ensure commands run correctly before you enable it in chat.

When creating custom tools from Python projects, manual dependency setup is not strictly required initially. The builder provides optional dependency setup guidance for Python projects only if and when it is needed during the creation process.

Creating custom tools requires explicit user approvals to enforce safety checks throughout the lifecycle. This validation mechanism ensures that all commands are clearly reviewed before enabling or promoting any tool generated from a repository.