tool-sync

Synchronize MCP tool documentation across six target files after tool changes.

24|8|Updated Dec 2, 2025
One-click install
npx skills add https://github.com/u9401066/pubmed-search-mcp --skill tool-sync
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tool-sync
Source: https://github.com/u9401066/pubmed-search-mcp/tree/main/.claude/skills/tool-sync
Command: npx skills add https://github.com/u9401066/pubmed-search-mcp --skill tool-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically keeps MCP tool documentation in sync whenever tools are added, removed, or renamed, ensuring alignment between code and docs and reducing manual drift.

Core Features & Use Cases

  • Automatic synchronization of TOOL_CATEGORIES in tool_registry.py when tools change to reflect new categories.
  • Automatic updates to registrations in tools/init.py to include new tools and reflect removals.
  • Automatic updates to the SERVER_INSTRUCTIONS tool list in instructions.py.
  • Automatic regeneration of Copilot instructions and documentation in .github/copilot-instructions.md.
  • Auto-refresh of the pubmed-mcp-tools-reference SKILL.md to reflect current tools.
  • Auto-update of README.md and README.zh-TW.md to reflect current tool counts.

Quick Start

Run the automated sync script to refresh all tool references and documentation.

Frequently Asked Questions about tool-sync

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

FAQPage Schema
How do I automatically sync MCP tool documentation when tools are added or removed?

Real-time documentation synchronization propagates tool changes across six target files, updating categories, registrations, and instructions to prevent manual drift between code and docs.

What is the best way to keep tool registry and documentation consistent after renaming tools?

Automated synchronization updates tool_registry.py, tools/__init__.py, and instructions.py simultaneously when tools are renamed, ensuring the tool registry and documentation remain perfectly aligned.

How does auto-syncing MCP tool references work for Copilot instructions and SKILL.md files?

Auto-syncing regenerates the Copilot instructions in .github/copilot-instructions.md and refreshes the pubmed-mcp-tools-reference SKILL.md to reflect current tool definitions and categories automatically.

Can I explicitly trigger a documentation refresh for MCP tools instead of relying on automatic detection?

Yes, you can explicitly trigger a documentation refresh for MCP tools through user-initiated sync commands, which propagate all tool definition changes to the six target files including README.md and README.zh-TW.md.

Does automating tool doc synchronization update the tool counts in README files?

Yes, automating tool doc synchronization updates the tool counts in both README.md and README.zh-TW.md, ensuring the documentation accurately reflects the current number of registered tools.