What is the difference between scripted smoke and manual-runtime checks?

Scripted smoke tests verify file existence and basic script integrity, while manual-runtime checks use provided documentation to ensure the tool's interface is functioning correctly.

What happens if a specific tool is not installed on my machine?

The verification process will mark that specific tool's status as SKIP rather than failing the entire audit.

Which tools does this skill support?

It supports auditing and verifying setups for Claude, Cursor, and Codex within the MDT (Model Driven Testing) framework.

Does mdt-dev-verify require an internet connection?

No, this skill is specifically designed to work locally and does not require authentication, network access, or live model sessions to perform smoke checks.

Can I use this skill if I haven't cloned the full MDT repository?

Yes, the skill supports an 'installed global tool mode' that targets local directories like ~/.codex/ for validation.

MDT Setup & Workflow Verifier

Name: MDT Setup & Workflow Verifier
Author: flatrick

byflatrick

0•

Security & Testing

Verifies MDT tool adapters and local workflow contracts to ensure environment readiness without requiring live model calls.

This skill provides a specialized auditing framework for the MDT agent harness, allowing developers to validate local tool setups for Claude, Cursor, and Codex. It bridges the gap between documented capabilities and actual local installations by running non-destructive smoke tests against a predefined workflow contract. It is particularly useful for verifying the integrity of local development environments, ensuring all necessary adapter files exist, and identifying discrepancies between documentation and implementation without the need for network access or CI pipelines.

Key Features

010 GitHub stars

02Dual-mode support for repository-specific and global tool installs

03Local workflow contract enforcement and validation

04Capability vs. implementation gap analysis and reporting

05Automated per-tool readiness reporting and manual checklist pointers

06Non-destructive scripted smoke testing for tool adapters

Use Cases

01Auditing local tool support and adapter integrity before starting development

02Generating offline readiness reports for team handoffs and environment debugging

03Validating environment setups and file existence after an MDT framework update

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add flatrick/mdt mdt-dev-verify

For use in Claude.ai and ChatGPT