Implement tdmcp tools with xSchema, xImpl, registerX, and offline unit tests.
npx skills add https://github.com/Pantani/tdmcp --skill tdmcp-tool-builder
Please help me install this Agent Skill. Skill: tdmcp-tool-builder Source: https://github.com/Pantani/tdmcp/tree/main/.agents/skills/tdmcp-tool-builder Command: npx skills add https://github.com/Pantani/tdmcp --skill tdmcp-tool-builder
Authoring a new tdmcp MCP tool is complex and boilerplate-heavy. This Skill provides a canonical, end-to-end blueprint to implement a tool using the standard file shape (XImpl + registerX), the Python-bridge pattern (buildPayloadScript/parsePythonReport), and the offline unit-test scaffolding, ensuring consistency with the project’s architecture and testing practices.
src/tools/layer2/manageComponent.ts.tests/unit that runs offline with msw to validate happy paths, fatal conditions, and bad input.Follow the canonical template in src/tools/layer*/ to create a new tool: implement xSchema, xImpl, and registerX, then add unit tests under tests/unit to validate the bridge workflow.
High-intent search queries and answers about installing and using this skill.
To reduce boilerplate when building a TypeScript MCP tool, use a single-file pattern with three exports (xSchema, xImpl, registerX) and a registrar to ensure consistent bridge-based execution and structured results.
The bridge pattern works by using buildPayloadScript and parsePythonReport with in-script guard logic, ensuring handlers do not throw runtime errors and return predictable structured results instead.
You can unit test an MCP tool offline by using msw (Mock Service Worker) to validate happy paths, fatal conditions, and bad input within your local test suite without external network dependencies.
The standard file structure for implementing an MCP tool involves defining xSchema, xImpl, and registerX in a single file under the src/tools directory, following NodeNext ES module conventions.
Yes, you need to configure Biome and NodeNext ES module conventions to ensure predictable tooling behavior, clear annotations, and consistent style across the tool implementation and testing scaffolding.
MCP tool handlers crash on bad input when robust guard TD error handling is missing; implementing non-throwing handlers with structured guard logic prevents crashes and ensures predictable results.
alicanerdoganRefactor code for clarity while preserving exact functionality.
beardcoderExecute Pest 4 tests to validate PHP/Laravel application behavior.
kraftvaerkMock Umbraco backoffice extension APIs with MSW v2 during testing.
daangnImplement unstyled, logic-only React headless components and custom hooks with namespace exports.