Skip to content
cccskills
FreePublished on GitHub

tdmcp-project-safety

Apply fail-closed consent, scope, undo, and verification rules to TouchDesigner mutations made with tdmcp.

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

Run score Not tested

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 project safety

Use this skill whenever a request can delete, overwrite, bypass, move, rename, save, or otherwise change artist-owned TouchDesigner state.

Safety rules

  • Fail closed. Missing UI, timeout, disconnect, close, malformed input, or broker failure is never approval for a destructive action.
  • Use native confirmation flows when the tool provides them. Preserve the exact decision in the structured result.
  • Never overwrite an existing project file without explicit consent.
  • Never call project load or quit unless a future, dedicated feature explicitly authorizes it.
  • Do not route panic, blackout, freeze, or other emergency controls through a confirmation queue.
  • Treat YOLO or confirmation skipping as an explicit policy flag. Report it; do not infer it from missing UI or environment state.
  • Keep bearer authentication and bridge authorization intact. Do not expose tokens, secrets, project contents, or raw script payloads in logs.

Mutation discipline

  1. Resolve exact paths and preconditions before writing.
  2. Describe scope and impact, including whether an operation destroys or merely bypasses state.
  3. Prefer one named undoable operation when the runtime proves that behavior. Do not promise cross-request atomic undo without live evidence.
  4. For multi-field edits, verify every applied field and roll back earlier fields if a later field fails.
  5. Read the final state back before returning success.

When TouchDesigner or the bridge is unavailable, continue with offline schema and unit validation but label live behavior UNVERIFIED — pending bridge.

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 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

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

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