Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

mdt-dev-verify

Étoiles1

Forks0

Mis à jour13 mars 2026 à 19:09

Verify MDT's shipped Codex setup against the local workflow contract. Use when auditing Codex support, checking whether installed setup files still exist, validating Codex workflow coverage, or producing a readiness report without relying on CI or live model calls.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

flatrick

flatrick/mdt

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Analystes en assurance qualité des logiciels et testeursProfessions informatiques et mathématiques·SOC 15-1253

Explorateur de fichiers

3 fichiers

SKILL.md

readonly

name	mdt-dev-verify
description	Verify MDT's shipped Codex setup against the local workflow contract. Use when auditing Codex support, checking whether installed setup files still exist, validating Codex workflow coverage, or producing a readiness report without relying on CI or live model calls.

MDT Dev Verify

When to Use

Use this skill when auditing MDT's local Codex adapter, validating documented Codex workflow coverage, or producing a Codex readiness report without relying on CI or live model calls.

Source Of Truth

In MDT repo mode, read these first:

docs/tools/capability-matrix.md
docs/tools/workflow-matrix.md
scripts/lib/tool-workflow-contract.js

In installed global tool mode:

read ~/.codex/skills/mdt-dev-verify/SKILL.md
read ~/.codex/mdt/scripts/lib/tool-workflow-contract.js
treat ~/.codex/ plus ~/.codex/mdt/ as the install surface
do not fail just because the full repo docs pack is absent

Required Workflow

MDT repo mode

Run mdt verify tool-setups.
If the Codex CLI is installed locally, run mdt dev smoke tool-setups.
Run mdt dev smoke workflows --tool codex.
If the scripted smoke passes, point to docs/testing/manual-verification/codex.md for the required real Codex session check.
Summarize results by workflow, by Codex readiness, and by any remaining manual-runtime checks.

Installed global tool mode

Run node ~/.codex/mdt/scripts/mdt.js dev smoke tool-setups.
Run node ~/.codex/mdt/scripts/mdt.js dev smoke workflows --tool codex.
Point to docs/testing/manual-verification/codex.md for the required real Codex session check.
Summarize readiness from the installed global surfaces and clearly separate scripted smoke from pending manual-runtime checks.

Rules

Do not rely on GitHub Actions or CI for this workflow.
Do not require authentication, network access, or a live model session to count a local smoke check as useful.
If the Codex CLI is not installed locally, mark its smoke status as SKIP.
If the docs and the contract disagree, fix the disagreement before expanding scope.
Do not treat script-only smoke output as proof that Codex runtime surfaces such as real-session patching are healthy.

Plus depuis ce dépôt

même dépôt

serena-mcp

flatrick/mdt

How to use the Serena MCP server for token-efficient code navigation, symbol analysis, and targeted editing. Use this skill whenever Serena tools are available (mcp__serena__* tools appear in your tool list), when exploring unfamiliar codebases, before editing any file larger than ~100 lines, when finding all callers of a function, or when you need to understand a module without reading it whole. ALWAYS prefer Serena's symbolic tools over raw Read calls for TypeScript, JavaScript, Python, or any language with LSP support — it is almost always faster and cheaper.

2026-03-151

context-mode

flatrick/mdt

Use context-mode tools (ctx_execute, ctx_execute_file) instead of Bash/cat when processing large outputs. Triggers: "analyze logs", "summarize output", "process data", "parse JSON", "filter results", "extract errors", "check build output", "analyze dependencies", "process API response", "large file analysis", "page snapshot", "browser snapshot", "DOM structure", "inspect page", "accessibility tree", "Playwright snapshot", "run tests", "test output", "coverage report", "git log", "recent commits", "diff between branches", "list containers", "pod status", "disk usage", "fetch docs", "API reference", "index documentation", "call API", "check response", "query results", "find TODOs", "count lines", "codebase statistics", "security audit", "outdated packages", "dependency tree", "cloud resources", "CI/CD output". Also triggers on ANY MCP tool output that may exceed 20 lines.

2026-03-151

ai-learning

flatrick/mdt

Instinct-based learning system for Codex. Manual-first: explicit capture and analysis baseline, with optional background observer.

2026-03-151

documentation-steward

flatrick/mdt

Keep repository documentation current, accurate, well-placed, and easy to follow for both humans and LLMs. Use when auditing doc drift, correcting stale claims, deciding where docs belong, or validating documentation quality before a commit.

2026-03-151

ai-learning

flatrick/mdt

Instinct-based learning system that adapts to the environment: hooks-passive observation for Claude/Cursor, explicit capture for hook-free tools. Single unified surface for all tools.

2026-03-151

documentation-steward

flatrick/mdt

2026-03-151

name	mdt-dev-verify
description	Verify MDT's shipped Codex setup against the local workflow contract. Use when auditing Codex support, checking whether installed setup files still exist, validating Codex workflow coverage, or producing a readiness report without relying on CI or live model calls.

MDT Dev Verify

When to Use

Use this skill when auditing MDT's local Codex adapter, validating documented Codex workflow coverage, or producing a Codex readiness report without relying on CI or live model calls.

Source Of Truth

In MDT repo mode, read these first:

docs/tools/capability-matrix.md
docs/tools/workflow-matrix.md
scripts/lib/tool-workflow-contract.js

In installed global tool mode:

read ~/.codex/skills/mdt-dev-verify/SKILL.md
read ~/.codex/mdt/scripts/lib/tool-workflow-contract.js
treat ~/.codex/ plus ~/.codex/mdt/ as the install surface
do not fail just because the full repo docs pack is absent

Required Workflow

MDT repo mode

Run mdt verify tool-setups.
If the Codex CLI is installed locally, run mdt dev smoke tool-setups.
Run mdt dev smoke workflows --tool codex.
If the scripted smoke passes, point to docs/testing/manual-verification/codex.md for the required real Codex session check.
Summarize results by workflow, by Codex readiness, and by any remaining manual-runtime checks.

Installed global tool mode

Run node ~/.codex/mdt/scripts/mdt.js dev smoke tool-setups.
Run node ~/.codex/mdt/scripts/mdt.js dev smoke workflows --tool codex.
Point to docs/testing/manual-verification/codex.md for the required real Codex session check.
Summarize readiness from the installed global surfaces and clearly separate scripted smoke from pending manual-runtime checks.

Rules

Do not rely on GitHub Actions or CI for this workflow.
Do not require authentication, network access, or a live model session to count a local smoke check as useful.
If the Codex CLI is not installed locally, mark its smoke status as SKIP.
If the docs and the contract disagree, fix the disagreement before expanding scope.
Do not treat script-only smoke output as proof that Codex runtime surfaces such as real-session patching are healthy.