skills.rest
JBODE-mhhs
JBODE-mhhsCOMMUNITY
Explore all skills by this author →
GitHub

tool-registration

Document new tools in TOOLS.md with command, purpose, flags, and examples.

Updated Aug 27, 2026
Search Tags:#automation#documentation#cli#register#tool#tools.md#bus-script
One-click install
npx skills add https://github.com/JBODE-mhhs/Zeus2.0-public --skill tool-registration-jbode-mhhs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tool-registration
Source: https://github.com/JBODE-mhhs/Zeus2.0-public/tree/main/templates/analyst/.claude/skills/tool-registration
Command: npx skills add https://github.com/JBODE-mhhs/Zeus2.0-public --skill tool-registration-jbode-mhhs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Tools arriving in the system often lack documentation, leaving agents unaware of how to use them. This skill standardizes the process of documenting new capabilities so teams can discover and leverage them quickly.

Core Features & Use Cases

  • Centralizes tool documentation for agents by guiding the update of TOOLS.md with command, purpose, and usage.
  • Ensures new bus scripts, CLIs, or API wrappers are reflected in a consistent reference across all workspaces.
  • Use Case: A developer adds a new internal API wrapper and registers it so agents can immediately understand its purpose and usage.

Quick Start

Add the new tool entry to TOOLS.md with its command, purpose, key flags, and usage examples.

Frequently Asked Questions about tool-registration

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

FAQPage Schema
How do I document new CLI tools so agents can discover them?▼

To document new CLI tools, you update TOOLS.md with a standardized entry containing the command, purpose, key flags, and usage examples so agents can discover and use them.

What is the best way to keep workspace tools in sync after adding new bus scripts?▼

Keeping workspace tools in sync after adding new bus scripts requires updating TOOLS.md with a minimal frontmatter-backed entry, ensuring consistent references across all workspace tools.

What should be included in tool documentation for automation scripts?▼

Tool documentation for automation scripts must include the command, purpose, key flags, and usage examples to standardize references and allow agents to immediately understand their capabilities.

Does registering an API wrapper require any specific environment setup?▼

Registering an API wrapper requires no specific environment setup; you simply add the new tool entry directly to TOOLS.md with its command, purpose, and usage details.

How do I standardize references for external integrations across workspaces?▼

You standardize references for external integrations by applying minimal frontmatter-backed guidelines to update TOOLS.md, ensuring all agents leverage consistent documentation across workspaces.

Related Skills

Explore More Software Engineering Skills→
jayteealaojayteealao

changelog-update

Generate changelog entries from git commits into Added, Changed, Fixed, and Breaking sections.

Community
Intermediate
reggiechan74reggiechan74
5

cli-reference

Document Claude Code CLI flags, options, and usage patterns.

Community
Basic
Sounder25Sounder25
27

MCP Connector

Expose the Antigravity Skills Library as MCP tools for external agents.

Community
Intermediate
ThomazRossitoThomazRossito
31

template

Create a ready-to-use Databricks skill scaffold with Markdown files and optional Python scripts.

Community
Basic