tdmcp-submission

Orchestrate a four-agent pipeline for tdmcp Connectors Directory submissions.

30|6|Updated May 25, 2026
One-click install
npx skills add https://github.com/Pantani/tdmcp --skill tdmcp-submission
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdmcp-submission
Source: https://github.com/Pantani/tdmcp/tree/main/.agents/skills/tdmcp-submission
Command: npx skills add https://github.com/Pantani/tdmcp --skill tdmcp-submission

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates the tdmcp Anthropic Connectors Directory (Desktop Extension / MCPB) submission prep — designs the package, writes the privacy page, migrates .dxt→.mcpb, drafts all form answers, and QAs the result. Use for ANY work on the tdmcp directory/marketplace submission, including re-runs after a rejection ("update the submission", "redo the form answers", "re-migrate the bundle", "fix the privacy page", "the directory rejected us"). Drives a 4-agent pipeline (architect → docs-author ∥ bundle-engineer → QA).

Core Features & Use Cases

  • Orchestrates a four-agent pipeline (architect → docs-author ∥ bundle-engineer → QA) to produce submission artifacts and a final QA report.
  • Manages a _workspace/ directory for inter-agent handoffs and audit trails.
  • Supports re-runs after rejection by guiding updates to privacy pages, migrations, and form answers.

Quick Start

Trigger the architect to produce the submission spec and then execute the full four-agent pipeline to create workspace artifacts and run QA.

Frequently Asked Questions about tdmcp-submission

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

FAQPage Schema
How do I prepare a submission for the Anthropic Connectors Directory?

A multi-agent pipeline submission orchestrates the entire submission workflow by coordinating an architect, docs-author, bundle-engineer, and QA agent. It automatically generates the submission spec, drafts the privacy page, migrates the bundle, and validates the final artifacts through a tracked pipeline.

What is the best way to migrate a Desktop Extension bundle to MCPB format?

The bundle-engineer agent within the four-agent pipeline handles the .dxt to .mcpb migration. It operates alongside a docs-author agent to ensure the migrated bundle and privacy page are properly staged in the workspace directory for subsequent QA validation.

Can I re-run a directory submission workflow after a rejection?

Yes, you can re-run the submission workflow after a rejection. The orchestration pipeline supports targeted updates to the privacy page, bundle migration, and form answers, allowing you to fix specific issues flagged by the directory without rebuilding the entire submission package.

Does the submission orchestration pipeline support multi-agent handoffs?

Yes, the submission orchestration pipeline supports multi-agent handoffs through a managed workspace directory. It facilitates artifact transfers between the architect, docs-author, bundle-engineer, and QA agents, maintaining an audit trail for spec creation, privacy drafts, and form answers.

Why does my Anthropic Connectors submission require a privacy page draft?

Your Anthropic Connectors submission requires a privacy page draft because the directory mandates clear privacy documentation for all listings. The docs-author agent drafts this page alongside the submission spec to ensure compliance before the QA agent validates the final package.