メニュー
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.
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.
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-creator |
| description | 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. |
Resolve every ../../scripts and ../../references path relative to this SKILL.md directory, never the caller working directory.
Create the smallest managed requirements layer that expresses the intended administrative constraint and still leaves a valid default for lower layers.
Identify the managed delivery channel (system /etc/codex/requirements.toml, Windows ProgramData, or macOS MDM com.openai.codex) and the exact policy being constrained.
Read ../../references/codex-artifact-contracts.md for the managed requirements surface and the allowed permission profiles.
Inspect options and generate a baseline:
python3 ../../scripts/create_codex_artifact.py requirements --help
python3 ../../scripts/create_codex_artifact.py requirements --output managed --name managed --description "Managed Codex requirements" --allowed-permission-profile :read-only --allowed-permission-profile :workspace
Constrain only what the policy requires. Keep a valid default: when default_permissions is unset, permit both :read-only and :workspace; otherwise make the default one of the allowed profiles.
Reference only built-in profiles or profiles the same file defines under [permissions.<name>]. Keep secrets and machine-local state out of the file.
Validate:
python3 ../../scripts/check_codex_artifact.py requirements managed/requirements.toml
Apply the file to a temporary managed layer with isolated HOME and CODEX_HOME and confirm the effective allowed-profile set without mutating live state.
[permissions.<name>].