skills.rest
MrWest3
MrWest3COMMUNITY
Explore all skills by this author →
GitHub

tool-registration

Document newly added tools in TOOLS.md with standardized entries.

Updated Aug 27, 2026
Search Tags:#documentation#cli#tooling#register#tools.md#bus-script
One-click install
npx skills add https://github.com/MrWest3/west-command-center --skill tool-registration-mrwest3
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tool-registration
Source: https://github.com/MrWest3/west-command-center/tree/main/templates/analyst/.claude/skills/tool-registration
Command: npx skills add https://github.com/MrWest3/west-command-center --skill tool-registration-mrwest3

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Newly added tools (tools, scripts, or integrations) are often undocumented, leaving agents unaware of capabilities and how to use them. This skill ensures they are formally documented in TOOLS.md so agents can discover and use them.

Core Features & Use Cases

  • Standardized templates in TOOLS.md for new tools to ensure consistency
  • Clear required fields (name, purpose, usage, key flags, examples) for each entry
  • Facilitates onboarding, cross-org consistency, and up-to-date tooling references
  • Use case: when a new bus script or CLI binary is introduced, add an entry so agents can immediately leverage it

Quick Start

Document a newly added tool by adding a properly formatted entry to TOOLS.md in the agent workspace.

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 binaries so agents can discover and use them?▼

To document new CLI binaries, you add a properly formatted entry to TOOLS.md containing the tool's name, purpose, usage, key flags, and example usage so agents can immediately discover and leverage the tool.

What's the best way to keep a TOOLS.md tool reference up to date across multiple orgs?▼

The best way to keep a TOOLS.md reference updated across orgs is to modify the file whenever a tool changes, ensuring standardized entries with required fields are maintained for cross-org consistency and agent discovery.

What required fields should a TOOLS.md entry include for a new bus script?▼

A TOOLS.md entry for a new bus script must include the tool's name, purpose, usage, key flags, and example usage to ensure agents understand its capabilities and can properly execute the script.

When do I need to update TOOLS.md for MCP servers and API wrappers?▼

You need to update TOOLS.md for MCP servers and API wrappers whenever a new tool is introduced or an existing tool changes, ensuring agents maintain awareness of available capabilities and integration methods.

Can I use standardized templates in TOOLS.md to ensure consistency for new tooling onboarding?▼

Yes, you can use standardized templates in TOOLS.md to ensure consistency during tooling onboarding, providing clear required fields that facilitate immediate discovery and usage by agents across the workspace.

Why are newly added tools often undiscoverable by agents in a workspace?▼

Newly added tools are often undiscoverable because they remain undocumented, leaving agents unaware of their capabilities and how to use them, which is solved by formally documenting them in TOOLS.md.

Related Skills

Explore More Software Engineering Skills→
grandameniumgrandamenium
88

tool-registration

Document newly added tools in each agent's TOOLS.md with command details.

Community
Basic
Executioner1939Executioner1939
8

new-releases-triage

Scan configured RSS/Atom/JSON feeds and GitHub trending sources for new engineering tools.

Community
Intermediate
PhilipDingPhilipDing
12

command

Compile a catalog of Linux commands with syntax and practical examples.

Community
Basic
jpoutrinjpoutrin
14

create-agent

Create Claude Code agent markdown files with required YAML frontmatter fields.

Community
Basic