mdt-dev-verify

Audit Claude, Cursor, and Codex setups against the local workflow contract.

1|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/flatrick/mdt --skill mdt-dev-verify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mdt-dev-verify
Source: https://github.com/flatrick/mdt/tree/main/skills/mdt-dev-verify
Command: npx skills add https://github.com/flatrick/mdt --skill mdt-dev-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill allows for the verification of MDT's tool setups and workflow coverage locally, without relying on external CI or live model calls, ensuring consistency and readiness.

Core Features & Use Cases

  • Local Auditing: Verify MDT's Claude, Cursor, and Codex setups against the local workflow contract.
  • Readiness Reporting: Generate per-tool readiness reports.
  • Use Case: Before deploying a new version of MDT, use this skill to quickly confirm that all tool configurations and scripts are functioning as expected on your local machine.

Quick Start

Run mdt verify tool-setups to audit local tool setups.

Frequently Asked Questions about mdt-dev-verify

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

FAQPage Schema
How do I verify Claude and Cursor tool setups locally without using CI?

You can verify Claude, Cursor, and Codex setups locally by running a command like mdt verify tool-setups, which audits tool support and checks setup file existence against your workflow contract without relying on GitHub Actions.

What is local workflow coverage auditing for coding tools?

Local workflow coverage auditing validates that your tool configurations and scripts align with your defined workflow contract, generating per-tool readiness reports to ensure consistency before deployment.

Can I check Codex setup file existence without live model calls?

Yes, you can validate Codex setup file existence and workflow coverage without executing live model calls, ensuring your tool configurations are structurally ready and functioning as expected offline.

Do I need GitHub Actions to generate per-tool readiness reports?

No, you do not need GitHub Actions to generate readiness reports, because this verification process runs entirely on your local machine and audits tool setups independently of external CI pipelines.

What's the best way to audit tool support for multiple coding assistants before a release?

The best way to audit tool support is to execute a local verification script that checks setup file existence and validates workflow coverage across Claude, Cursor, and Codex simultaneously to produce readiness reports.