plugin-creator
Create and scaffold plugin directories for Codex with a required `.codex-plugin/plugin.json`, optional plugin folders/files, and baseline placeholders you can edit before publishing or testing. Use when Codex needs to create a new local plugin, add optional plugin structure, or generate or update repo-root `.agents/plugins/marketplace.json` entries for plugin ordering and availability metadata.
Security Assessment
About plugin-creator
Plugin Creator is a scaffolding skill for building Codex plugins. It solves the boilerplate problem of standing up a correctly-structured plugin directory: it always produces the required `.codex-plugin/plugin.json` manifest with the full schema shape, placeholder values, and the complete `interface` section, so authors can fill in `[TODO: ...]` placeholders rather than assembling the layout by hand. It can also generate or update the repo-root `.agents/plugins/marketplace.json` that controls plugin ordering and availability metadata in the Codex UI.
The skill drives a bundled Python script, `scripts/create_basic_plugin.py`, that normalizes the plugin name to lower-case hyphen-case, creates the plugin root and manifest, and optionally scaffolds companion folders (`skills/`, `hooks/`, `scripts/`, `assets/`, `.mcp.json`, `.app.json`) via flags such as `--with-skills` and `--with-marketplace`. It supports both repo-local and home-local plugin locations, asking the user which they want before generating marketplace entries. Marketplace entries default to `policy.installation: AVAILABLE` and `policy.authentication: ON_INSTALL`, always include a category, and are appended rather than reordered unless the user asks otherwise. A reference spec documents every manifest and marketplace field.
It targets plugin developers and teams publishing to a Codex marketplace who want consistent, spec-conformant plugin scaffolding and correctly-formed availability metadata. Use cases include creating a new local plugin, adding optional plugin structure to an existing one, and registering a plugin in the marketplace catalog.
FAQ
What does the scaffold actually create?
A plugin root folder plus a required `.codex-plugin/plugin.json` manifest filled with the full schema and placeholders, and optionally companion folders like skills, hooks, scripts, assets, a `.mcp.json`, a `.app.json`, and a marketplace entry.
How do I run it?
Run the Python script from the repo root, for example `python3 .agents/skills/plugin-creator/scripts/create_basic_plugin.py <plugin-name>`, adding `--with-marketplace` and other flags to include optional structure.
Where does marketplace.json live?
Always at `<repo-root>/.agents/plugins/marketplace.json` for repo plugins, or `~/.agents/plugins/marketplace.json` for home-local plugins.
What are the default policy values for new entries?
New marketplace entries default to `policy.installation: AVAILABLE` and `policy.authentication: ON_INSTALL`, with a category always included; defaults are overridden only when the user explicitly requests another allowed value.
Does it reorder existing marketplace plugins?
No. It appends new entries and preserves existing order unless the user explicitly asks to reorder, since plugin order determines render order in Codex.
Install plugin-creator
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
openai/skills