te-doctor

Diagnose and resolve Claudikins Tool Executor build, MCP connectivity, registry, and workspace issues.

63|7|Updated Jan 12, 2026
One-click install
npx skills add https://github.com/elb-pr/claudikins-tool-executor --skill te-doctor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: te-doctor
Source: https://github.com/elb-pr/claudikins-tool-executor/tree/main/skills/te-doctor
Command: npx skills add https://github.com/elb-pr/claudikins-tool-executor --skill te-doctor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires typescript, @types/node, jest, ts-jest, rimraf, semver, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps users diagnose and resolve problems encountered when using the Claudikins Tool Executor, ensuring smooth operation of AI-driven tool interactions.

Core Features & Use Cases

  • Health Checks: Run comprehensive test suites to verify the Tool Executor's functionality.
  • Diagnostic Steps: Follow a structured checklist to pinpoint issues related to build status, server connectivity, registry integrity, and workspace state.
  • Common Issue Resolution: Provides specific fixes for frequent problems like "search_tools returns no results" or "execute_code times out".
  • Use Case: A user reports that search_tools is not returning any relevant tools. They can use this Skill to run the build, check registry integrity, and test Serena health to identify and fix the root cause.

Quick Start

Run the test suite to verify everything works.

Frequently Asked Questions about te-doctor

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

FAQPage Schema
How do I troubleshoot Claude Code MCP server connectivity and tool execution issues?

Troubleshoot Claude Code MCP server issues by running comprehensive test suites and following a structured diagnostic checklist covering build status, server connectivity, registry integrity, and workspace state to pinpoint root causes.

Why does search_tools return no results when using the Tool Executor?

When search_tools returns no results, check registry integrity and test Serena health to identify and resolve the root cause of the failed tool discovery process.

How do I diagnose execute_code timeout errors in a Claude Code MCP setup?

Diagnose execute_code timeouts by following structured diagnostic steps for MCP server connectivity and workspace state to resolve execution delays.

Do I need Node.js 18+ to run diagnostic tests for Tool Executor troubleshooting?

Yes, Node.js 18+ is required to run the specific npm scripts for testing and rebuilding the Tool Executor environment during troubleshooting.

What is the best way to verify Claudikins Tool Executor functionality after a build failure?

Verify Tool Executor functionality by running comprehensive health checks and test suites to confirm build status, registry integrity, and MCP server connectivity.

Can I use Jest and TypeScript to test Tool Executor registry integrity and resolve client connection errors?

Yes, the Tool Executor uses Jest and TypeScript to run test suites that verify registry integrity and diagnose MCP client connection errors.