メニュー
Check Codex MCP JSON or TOML definitions, transport completeness, launcher provenance, environment handling, and runtime connectivity. Use before enabling, bundling, or releasing an MCP server.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Start here for the nddev-builder toolkit. Indexes the Codex artifact families and the creator, checker, reviewer, and workflow skill that owns each, points at the single reference for schemas and current (Beta, experimental, or under-development) surfaces, and routes the task to the right skill. Use first whenever building, checking, reviewing, or releasing a Codex artifact, or when unsure which builder skill applies.
A guided first run of the nddev-builder toolkit — from zero to a working, checked Codex artifact in ordered steps. Use when new to nddev-builder, onboarding, or unsure which builder skill to start with.
Create or revise a Codex marketplace catalog with valid plugin sources, categories, installation policy, and authentication policy. Use when publishing local or remote plugin collections.
Check a managed Codex requirements.toml layer for supported keys, permission-profile consistency, and a valid lower-layer default. Use before delivering managed /etc/codex or MDM requirements.
Create a managed Codex requirements.toml layer that constrains permission profiles and other admin policy. Use when authoring the /etc/codex or MDM-delivered managed requirements a lower config layer must satisfy.
Install and iterate on a Codex plugin locally in developer mode: the install, reinstall, and cachebuster test loop for a plugin under development, run against an isolated install and never live state. Use when running or iterating on a plugin, its skills, MCP, hooks, or bundled app locally.
| name | codex-mcp-checker |
| description | Check Codex MCP JSON or TOML definitions, transport completeness, launcher provenance, environment handling, and runtime connectivity. Use before enabling, bundling, or releasing an MCP server. |
Resolve every ../../scripts and ../../references path relative to this SKILL.md directory, never the caller working directory.
Validate the source definition, then prove the declared transport can initialize without leaking live credentials.
Identify whether the definition is plugin .mcp.json or Codex config TOML and read ../../references/codex-artifact-contracts.md.
For a plugin definition, run:
python3 ../../scripts/check_codex_artifact.py mcp .mcp.json
Check stable unique names, required transport fields, explicit argv, valid cwd and paths, pinned mutable launchers, and complete disabled-server metadata.
Reject inline tokens, secrets, synthetic inherited servers, ambiguous shell strings, and missing authentication ownership.
Use a temporary HOME and CODEX_HOME with stub credentials. Start stdio servers or perform HTTP initialization, list tools, and exercise one safe read-only call when available.
Confirm failures are actionable and do not hang indefinitely.
Return PASS only when schema, security review, and available connectivity checks succeed. Otherwise return FAIL with server name, field or runtime evidence, and correction.