add-tool

Add a ToolConfig entry to toolbox-core's default_tools() and verify with cargo check.

Updated Jan 24, 2026
One-click install
npx skills add https://github.com/ereferen/zellij-toolbox --skill add-tool
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-tool
Source: https://github.com/ereferen/zellij-toolbox/tree/main/.claude/skills/add-tool
Command: npx skills add https://github.com/ereferen/zellij-toolbox --skill add-tool

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Toolbox users want to extend the default toolset without editing multiple source files manually; this Skill provides a guided workflow to add a new tool definition to toolbox-core's default tools.

Core Features & Use Cases

  • Adds a new ToolConfig entry with name, command, parse_regex, icon, enabled, and short_name.
  • Locates the default_tools function and ensures changes compile with cargo check.
  • Use case: extend supported tools in a project to track versions and commands centrally.

Quick Start

Use /add-tool <name> <command> to add a new tool definition to the default tools, then run cargo check to verify compilation.

Frequently Asked Questions about add-tool

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

FAQPage Schema
How do I add a new tool definition to toolbox-core default tools?

To add a new tool definition, edit toolbox-core/src/config.rs, locate the default_tools() function, and insert a new ToolConfig struct with name, command, parse_regex, icon, enabled, and short_name fields.

What fields are required for a ToolConfig entry in Rust?

A ToolConfig entry requires name, command, parse_regex, icon, enabled, and short_name fields to properly define the tool's execution and parsing behavior within the default tools configuration.

How do I verify my Rust toolbox configuration changes compile correctly?

After inserting a new ToolConfig into default_tools(), run cargo check to verify that the Rust configuration changes compile successfully without syntax or type errors in toolbox-core.

When do I need to extend toolbox-core with custom tool definitions?

You need to extend toolbox-core with custom tool definitions when you want to centrally track versions and commands for additional tools across a project without editing multiple source files manually.

Does adding a custom tool to toolbox-core require modifying multiple files?

No, adding a custom tool definition only requires editing the toolbox-core/src/config.rs file to insert a new ToolConfig entry into the default_tools() function, followed by running cargo check.

Can I use per-project configurations when adding tools to toolbox-core?

Yes, the add-tool workflow supports customizing the toolbox for per-project configurations by inserting specific ToolConfig definitions into the default_tools() function within config.rs.