skills.rest
orient-bot
orient-botOFFICIAL
Explore all skills by this author →
GitHub

tool-executor-registry-migration

Migrate Orient tools from switch statements to the ToolExecutorRegistry handler pattern.

Updated Aug 27, 2026
Search Tags:#typescript#refactoring#developer guide#mcp-server#orient#tool migration
One-click install
npx skills add https://github.com/orient-bot/orient --skill tool-executor-registry-migration
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tool-executor-registry-migration
Source: https://github.com/orient-bot/orient/tree/main/.claude/skills/tool-executor-registry-migration
Command: npx skills add https://github.com/orient-bot/orient --skill tool-executor-registry-migration

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill guides developers through the process of migrating Orient tools from legacy switch statements to the modern ToolExecutorRegistry handler pattern, ensuring tools function correctly with modular servers.

Core Features & Use Cases

  • Migration Guide: Provides step-by-step instructions for moving tools.
  • Architecture Explanation: Details the ToolRegistry (discovery) and ToolExecutorRegistry (execution) systems.
  • Debugging Assistance: Helps identify and resolve "Unknown tool" errors.
  • Use Case: A developer needs to update an existing tool in Orient to work with the latest server architecture. This Skill provides the exact steps, code examples, and common pitfalls to avoid during the migration.

Quick Start

Follow the migration steps outlined in this skill to move a tool from the legacy switch statement to the ToolExecutorRegistry.

Frequently Asked Questions about tool-executor-registry-migration

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

FAQPage Schema
What is the ToolExecutorRegistry handler pattern in Orient?▼

The ToolExecutorRegistry is the execution system for modular MCP servers, while the ToolRegistry handles discovery. Migrating to this two-registry architecture replaces legacy switch statements to enable modular tool execution.

Why do I get an "Unknown tool" runtime error after updating my Orient MCP server?▼

An "Unknown tool" runtime error occurs when tool implementations are not properly registered within the ToolExecutorRegistry. Debugging this migration requires ensuring tools are moved from legacy switch statements to the correct handler pattern.

Do I need TypeScript to refactor Orient tools for modular MCP server types?▼

Refactoring Orient tools for modular MCP server types involves TypeScript implementation patterns. Developers update existing tool implementations by moving them into the ToolExecutorRegistry to ensure tools function correctly with modular servers.

What is the best way to resolve "Unknown tool" errors during tool migration?▼

The best way to resolve "Unknown tool" errors is to verify the two-registry architecture setup. Ensure the tool is discoverable by the ToolRegistry and correctly mapped to a handler in the ToolExecutorRegistry during migration.

Related Skills

Explore More Software Engineering Skills→
gaia-reactgaia-react
21

typescript

Standardize TypeScript naming conventions, explicit return types, and Zod 4 schemas.

Official
Advanced
richardwoodingrichardwooding
5

add-mcp-tool

Extend an MCP server with custom tools using Go structs and handlers.

Community
Intermediate
benjaminshoemakerbenjaminshoemaker
39

oauth-login

Automate OAuth login for Google and GitHub with local callback and token storage.

Community
Advanced
KrishpotanwarKrishpotanwar

V3 DDD Architecture

Convert monolithic codebases into modular domain-oriented architecture with bounded contexts.

Community
Advanced