メニュー
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.
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.
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.
Version, catalog, and publish a native Codex plugin for distribution — the release step after dev-test, covering the SemVer manifest bump, marketplace catalog update, distribution source, and portal submission.
| name | codex-requirements-checker |
| description | 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. |
Resolve every ../../scripts and ../../references path relative to this SKILL.md directory, never the caller working directory.
Validate the managed requirements layer in its delivery scope and inspect the effective constraint it imposes, not merely TOML syntax.
Identify the managed delivery channel (system /etc/codex/requirements.toml, Windows ProgramData, or macOS MDM com.openai.codex) and read ../../references/codex-artifact-contracts.md.
Run:
python3 ../../scripts/check_codex_artifact.py requirements managed/requirements.toml
Check supported top-level keys, the allowed_permission_profiles table shape, and that every referenced profile is a built-in or defined under [permissions.<name>].
Confirm a valid default remains: default_permissions must be one of the allowed profiles, or, when unset, the allowed set must permit both :read-only and :workspace.
Fail any layer that mixes permission-profile settings with legacy sandbox settings, or that carries deprecated or secret-bearing keys.
Apply the file to a temporary managed layer with isolated HOME and CODEX_HOME; confirm the effective allowed-profile set or diagnostics.
Return PASS only when static consistency and available runtime confirmation succeed. Otherwise return FAIL with the key path, the effective constraint risk, and the correction.