What problem does it solve? Developers building Codex plugins often struggle with where to place manifests, commands, agents, skills, and hooks, and how to configure auto-discovery and portable paths. This Skill provides the canonical directory layout, plugin.json configuration rules, and naming conventions so plugins load correctly on the first try. ## Core Features & Use Cases - Standardized Directory Layout: Defines the required .Codex-plugin/plugin.json manifest location and root-level component directories for commands, agents, skills, and hooks. - Manifest Configuration: Documents required and recommended plugin.json fields, custom component paths, semantic versioning, and kebab-case naming rules. - Portable Path References: Explains how to use ${CLAUDE_PLUGIN_ROOT} in hooks, MCP server definitions, and scripts so plugins work across operating systems and install methods. - Use Case: When scaffolding a new plugin with a slash command, a subagent, and a PreToolUse hook, follow this Skill to place each file correctly, write the manifest, and reference hook scripts portably. ## Quick Start Ask the AI to scaffold a new Codex plugin named code-review-assistant with one command, one agent, and a hook, following the standard plugin structure.