One-click install
npx skills add https://github.com/pycode4micro/bushserver --skill tool-maintainer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tool-maintainer
Source: https://github.com/pycode4micro/bushserver/tree/main/src/bushserver/seeds/skills/package/tool-maintainer
Command: npx skills add https://github.com/pycode4micro/bushserver --skill tool-maintainer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you keep BushServer’s tool system and MCP gateway inventory correct when you need to add, install, update, enable/disable, repair, or remove tools and MCP server records.

Core Features & Use Cases

  • Builtin tool package lifecycle control: Manage builtin tool packages stored under $BUSH_DATA_DIR/tools, including installation, enable/disable, updates, and health/registration repair.
  • MCP server record lifecycle control: Add, install, enable/disable, update, repair, or remove MCP server records in $BUSH_DATA_DIR/tool_gateway/servers.json with server-scoped handling.
  • State inspection with runtime truth: Verify whether a builtin tool or MCP server is installed, enabled, broken, removable, and aligned between manifests and runtime directories without guessing.

Quick Start

Tell the skill exactly what builtin tool package or MCP server you want to add, update, repair, or enable/disable, and it will apply the authoritative manager-driven change instead of generic Q&A.

Frequently Asked Questions about tool-maintainer

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

FAQPage Schema
How do I manage MCP server records in BushServer without breaking the gateway configuration?

To manage MCP server records safely, use manager-driven actions to add, update, or remove entries in the servers.json control-plane file, avoiding direct hand-editing to ensure runtime alignment.

What is the best way to repair broken builtin tool registration in BushServer?

The best way to repair broken builtin tool registration is to apply authoritative health verification and repair actions, which realigns package manifests with the runtime directories under $BUSH_DATA_DIR/tools.

Can I enable or disable MCP servers on a per-server scope?

Yes, you can enable or disable MCP servers on a server-scoped basis by applying lifecycle operations directly to the targeted server records within the tool gateway inventory.

How do I verify if a BushServer tool package is installed and aligned with its runtime directory?

You can verify installation and alignment by inspecting the runtime truth, which checks whether the builtin tool package manifest and the runtime directory state are synchronized and healthy.

Why should I avoid directly editing the control-plane JSON for MCP server configuration?

Avoiding direct edits to control-plane JSON prevents configuration drift and misalignment, ensuring that package manifests and runtime directories stay synchronized through dedicated manager actions.

What limitations exist when removing builtin tool packages from the runtime environment?

Removal limitations depend on verifying whether the builtin tool is removable and aligned, requiring state inspection to confirm no runtime dependencies exist before modifying the tool system.