Orchestrate any tdmcp test-coverage work: run the coverage harness, inspect coverage gaps, plan focused Vitest/msw or bridge tests, delegate coverage writers, verify coverage deltas, and re-run gates. Use whenever the user asks to raise coverage, add broad regression coverage, create a test harness, improve tests, re-run a coverage wave, or fix a coverage gate.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Use this skill for coverage-improvement work in this repository. The goal is more tested behavior, not prettier percentages.
CLAUDE.md, package.json, vitest.config.ts, and the nearest tests.npm run coverage:harness unless the user asked for a static-only pass._workspace/coverage/latest.md.src/**/*.ts; src/knowledge/data/** is
generated reference data and is intentionally excluded.Choose one to three independent gaps. Prefer seams where a test can lock a real contract:
isError
paths using msw.Skip generated data, docs-only files, and import-only tests.
For parallel work, spawn tdmcp-coverage-writer agents with one seam each. Give
each writer:
The lead is the single writer for shared config, package scripts, and harness docs. Do not let multiple agents edit the same test file.
Run narrow tests first. Then run:
npm run typecheck
npm run build
./node_modules/.bin/biome check .
npm run coverage:harness
npm run validate:recipes
npm run test:bridge
If a gate fails, fix forward. Do not lower coverage thresholds, delete assertions, or exclude executable code to pass.
Write _workspace/coverage/wave-<date>.md with:
_workspace/coverage/latest.md.src/cli/chat.ts; writer adds focused
CLI behavior tests; lead runs coverage and gates; report includes delta.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Write operator-facing and public documentation plans for AI-Controlled Party mixer/Soundcraft Ui24R scene arming. Use for runbooks, rehearsal checklists, show-day checklists, EN/PT docs updates, demo scripts, safety wording, and follow-up documentation revisions.
The English summary is being prepared. Showing the original description.
Authoritative reference for submitting tdmcp to the Anthropic Connectors Directory as a Claude Desktop Extension (MCPB). Use whenever drafting, checking, or fixing the submission — it defines the two submission paths, why tdmcp is a Desktop Extension (never a remote connector), every form field, the rejection-causing gates, and the local-only compliance story. Read this before writing any submission deliverable.
The English summary is being prepared. Showing the original description.
Authoritative reference for submitting tdmcp to the Anthropic Connectors Directory as a Codex Desktop Extension (MCPB). Use whenever drafting, checking, or fixing the submission — it defines the two submission paths, why tdmcp is a Desktop Extension (never a remote connector), every form field, the rejection-causing gates, and the local-only compliance story. Read this before writing any submission deliverable.
The English summary is being prepared. Showing the original description.
How to migrate the tdmcp Claude Desktop bundle from legacy .dxt to .mcpb (MCP Bundle) and keep it building — covers the manifest schema (verify against the installed packer, never hardcode), the build-mcpb.mjs packer/zip-fallback flow, the npm scripts, and the full .dxt→.mcpb reference sweep across docs and scripts. Use when packaging or migrating the tdmcp desktop bundle.
The English summary is being prepared. Showing the original description.
How to migrate the tdmcp Codex Desktop bundle from legacy .dxt to .mcpb (MCP Bundle) and keep it building — covers the manifest schema (verify against the installed packer, never hardcode), the build-mcpb.mjs packer/zip-fallback flow, the npm scripts, and the full .dxt→.mcpb reference sweep across docs and scripts. Use when packaging or migrating the tdmcp desktop bundle.
The English summary is being prepared. Showing the original description.
Review, harden, and test the safety policy for AI-Controlled Party mixer/Soundcraft Ui24R scene arming. Use for approval gates, blocked mixer operations, hazardous request handling, venue validation, bypass attempts, QA, risk review, or follow-up safety changes.
The English summary is being prepared. Showing the original description.