submission-qa

Validate MCP submission packages with gate-based checks and command transcripts.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Gate-checking for MCP submission packages ensures completeness, compliance, and reproducibility by executing commands and quoting outputs to prevent human error and backlogs.

Core Features & Use Cases

  • Automated gate checks including docs build, bundle creation, manifest validation, version checks, and stale-reference sweeps.
  • Reproducible evidence generation with transcripts, leading to a final QA report at _workspace/03_qa-report.md.
  • Clear, actionable feedback for submitters and docs/authors to fix issues before submission.

Quick Start

Run the submission QA process on your package to produce a gate report with command transcripts.

Frequently Asked Questions about submission-qa

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

FAQPage Schema
How do I run automated gate checks for MCP submission packages?

Automated gate checks for MCP submission packages are executed via a gate-based verification workflow that validates docs build, bundle creation, manifest sanity, stale references, and annotations. It outputs a structured QA report with command transcripts as evidence.

What is a gate-based verification workflow for submission bundles?

A gate-based verification workflow for submission bundles sequentially executes checks like docs:build, bundle:build, and manifest sanity. It quotes command outputs to provide reproducible evidence, preventing human error and backlogs during pre-submission validation.

How do I validate manifest sanity and stale references before submitting connectors?

Manifest sanity and stale references are validated by running CI-like verification steps on the connectors directory. The process sweeps for stale references and checks annotations, generating actionable feedback and a final report at _workspace/03_qa-report.md.

Does the MCP submission QA process generate reproducible evidence for CI-like steps?

The MCP submission QA process generates reproducible evidence by quoting command outputs from CI-like steps into transcripts. This ensures completeness and compliance, producing a structured _workspace/03_qa-report.md with evidence for submitters and docs authors.

What's the best way to prevent backlogs in MCP package compliance checks?

Preventing backlogs in MCP package compliance checks is achieved by automating pre-submission validation through a gate-based workflow. It executes docs and bundle builds, validates manifests, and provides clear, actionable feedback to fix issues before submission.

Can I use this submission QA workflow to check docs build and bundle creation?

You can use this submission QA workflow to check docs build and bundle creation through dedicated implementation gates. It applies to pre-submission checks for the connectors directory, ensuring reference integrity across CI-like steps before generating a QA report.