メニュー
Create or revise native Codex plugins with valid manifests and intentionally bundled skills, apps, MCP servers, or hooks. Use when building a distributable Codex plugin rather than standalone files.
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-plugin-creator |
| description | Create or revise native Codex plugins with valid manifests and intentionally bundled skills, apps, MCP servers, or hooks. Use when building a distributable Codex plugin rather than standalone files. |
Resolve every ../../scripts and ../../references path relative to this SKILL.md directory, never the caller working directory.
Build a minimal plugin whose manifest and bundled capabilities form one coherent product boundary.
Define the plugin's purpose, installation scope, bundled capabilities, and authentication requirements.
Prefer the built-in $plugin-creator for first-party scaffolding and manifest guidance.
Read ../../references/codex-artifact-contracts.md before selecting directories or manifest fields.
If a scaffold is still needed, inspect options and run:
python3 ../../scripts/create_codex_artifact.py plugin --help
python3 ../../scripts/create_codex_artifact.py plugin --output plugins --name example-plugin --description "Bundle focused Codex development workflows"
Keep .codex-plugin/plugin.json at the plugin root. Add only capabilities the plugin actually owns.
Use native skills for workflows; do not copy Claude or OpenCode slash commands.
Keep custom agents as standalone TOML under .codex/agents/ or CODEX_HOME/agents/, not inside the plugin bundle.
Validate the complete plugin:
python3 ../../scripts/check_codex_artifact.py plugin plugins/example-plugin
If Codex is available, install from an isolated marketplace and verify discovery without touching live user state.