skills.rest
flatrick
flatrickCOMMUNITY
Explore all skills by this author →
GitHub

mdt-dev-smoke

Execute automated smoke tests for MDT development installations in Codex.

1|Updated Mar 4, 2026
Search Tags:#automation#development#verification#codex#smoke test#mdt
One-click install
npx skills add https://github.com/flatrick/mdt --skill mdt-dev-smoke
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mdt-dev-smoke
Source: https://github.com/flatrick/mdt/tree/main/codex-template/skills/mdt-dev-smoke
Command: npx skills add https://github.com/flatrick/mdt --skill mdt-dev-smoke

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides a quick and automated way to verify the integrity of an MDT development setup within the Codex environment, ensuring essential scripts and workflows are functioning correctly.

Core Features & Use Cases

  • Automated Verification: Runs predefined smoke tests for MDT development installations in Codex.
  • Environment Sanity Check: Helps identify common issues after a --dev install or when a setup might have drifted.
  • Use Case: After installing MDT with the --dev flag for Codex, run this skill to confirm that the core development scripts execute without errors and that the basic workflow commands are recognized and functional.

Quick Start

Run the installed MDT Codex dev smoke checks.

Frequently Asked Questions about mdt-dev-smoke

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

FAQPage Schema
How do I run an automated smoke test for an MDT development installation in Codex?▼

You can run an automated smoke test for an MDT development installation in Codex by executing the mdt-dev-smoke skill. This verifies that core development scripts and workflow commands function correctly without errors after a --dev install.

What is an MDT dev smoke check and when do I need to run it?▼

An MDT dev smoke check is an automated verification process for MDT development setups in Codex. You need to run it after installing MDT with the --dev flag or whenever a setup might have drifted, to identify common environment issues and ensure basic workflow commands are recognized.

Do I need Node.js to verify MDT development scripts in the Codex environment?▼

Yes, you need Node.js to verify MDT development scripts in the Codex environment. The smoke test execution requires the Node.js runtime and strict adherence to the MDT contract to successfully validate the functionality of core development scripts.

What is the best way to check if MDT core development workflows are functioning after installation?▼

The best way to check if MDT core development workflows are functioning after installation is to run automated smoke tests. This verifies the integrity of the MDT development setup in Codex, confirming that essential scripts execute without errors and workflow commands are recognized.

Why does my MDT development setup drift and how can I identify the issue?▼

An MDT development setup can drift over time due to environment changes, and you can identify the issue by running an automated smoke check. This environment sanity check validates post-installation functionality and helps pinpoint common script or workflow errors in Codex.

Related Skills

Explore More Software Engineering Skills→
lpjhelderlpjhelder

forge-setup

Install and configure kronon-forge with Node.js and npm.

Community
Intermediate
tianjianjiangtianjianjiang
1

smith-validation

Performs hypothesis testing and root cause analysis to debug software systems.

Community
Advanced
FlexNetOSFlexNetOS

plugin-creator

Generate Codex plugin structures and marketplace entries with Python scripts.

Official
Intermediate
cropsggcropsgg
15

accessibility-audit

Automate WCAG 2.1 AA accessibility checks with axe-core and jsx-a11y.

Community
Advanced