Skip to content
cccskills
FreePublished on GitHub

tdmcp-troubleshooting

Diagnose tdmcp and TouchDesigner bridge problems with bounded checks and evidence-backed recovery steps.

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md1.7 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

tdmcp troubleshooting

Use this skill when tdmcp cannot reach TouchDesigner, a structured operation fails, a node cooks with errors, or the observed network differs from the requested result.

Diagnose in layers

  1. Check local runtime status: package version, configuration source, bridge URL, authentication readiness, and whether the endpoint is reachable.
  2. If reachable, read bridge info and TouchDesigner build before testing mutating operations.
  3. Inspect the exact operator path, parameters, connections, cook errors, and preview relevant to the failure.
  4. Distinguish unsupported endpoint, invalid input, authorization failure, timeout, connection refusal, and TouchDesigner-side error. Do not collapse them into "offline".
  5. Reproduce with the smallest structured read or mutation. Do not use arbitrary Python merely to bypass a missing first-class operation.

Recovery boundaries

  • Do not disable authentication or enable raw execution as a generic repair.
  • Do not delete or overwrite artist content to make a health check pass.
  • Preserve the configured bridge port; parallel analysis or test bridges must use isolated ports.
  • After a repair, repeat the original bounded check and report both the prior failure and current evidence.
  • If a check requires a running UI, hardware, pane, or saved project, mark it unverified when that dependency is absent.

Useful evidence includes exact endpoint status, typed error code, operator path, parameter name, TouchDesigner build, and the command or tool result that verified recovery. Redact tokens and project-sensitive content.

Reviews

No reviews yet. Tell others what you thought.

Comments

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.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

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.

Pantani/tdmcp53Updated Aug 16, 2026

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.

Pantani/tdmcp53Updated Aug 16, 2026

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.

Pantani/tdmcp53Updated Aug 16, 2026

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.

Pantani/tdmcp53Updated Aug 16, 2026

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.

Pantani/tdmcp53Updated Aug 16, 2026

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.

Pantani/tdmcp53Updated Aug 16, 2026

See all skills by Pantani

Report a problem with this skill