Codex Plugin Creator
Scaffold Codex plugins with a standard manifest, optional components, and marketplace metadata.
The evidence shows local directory creation, JSON writes, and optional marketplace updates, with --force required for overwrites. However, least-privilege path boundaries, rollback, sensitive-data handling, and pre-write confirmation are not established, so 11 points are deducted.
The documentation, script, and candidate Skill versions materially conflict: the supplied script defaults to the current repository and emits TODO placeholders, while several scripts and options referenced by the candidate are absent from the supplied evidence. No tests or abnormal-input coverage are shown, so 14 points are deducted.
The audience and scenarios—plugin scaffolding, personal or team marketplaces, and optional component directories—are reasonably clear, with some non-fit guidance. Trigger semantics, input/output contracts, and environment evidence remain limited, and Chinese-language support is not stated, so 7 points are deducted.
The material provides quick-start instructions, workflows, field rules, references, and validation guidance. Versioning, changelog, explicit maintenance ownership, license, and complete dependency documentation are missing, and referenced files are not all supplied, so 8 points are deducted.
The core purpose—creating a plugin skeleton and marketplace entry—has a directly usable intended output. However, the candidate documentation does not match the supplied script, and the validation and update helpers cannot be confirmed from the evidence; generated output still requires manual correction or verification, so 10 points are deducted.
The script source and specification samples provide some auditable primary evidence, but there is no committed test suite, CI coverage, or third-party execution evidence, and key referenced files are missing, so 7 points are deducted.
- The supplied material contains conflicting Skill and script versions; verify the scripts, options, and referenced files at the target revision before use.
- The script writes to local directories and supports --force overwrites without documented transactional updates, backups, or recovery.
- Do not publish generated placeholder or unverified manifests; complete metadata and run an available validator first.
- No license file or explicit version-maintenance information is supplied; license metadata should be treated as unknown.
What it does & when to use it
This skill creates and maintains the baseline structure for Codex plugins. It always generates `.codex-plugin/plugin.json` and can optionally add skills, hooks, scripts, assets, MCP, and app configuration entries. With the marketplace option, it creates or updates a repository-level `marketplace.json` for plugin ordering and availability metadata. Plugin names are normalized to lowercase hyphen-case and limited to 64 characters.
Runs create_basic_plugin.py to create a plugin directory and plugin.json with the full schema shape and placeholders; optionally creates skills/, hooks/, scripts/, assets/, .mcp.json, and .app.json; with --with-marketplace, creates or updates .agents/plugins/marketplace.json with source, installation policy, authentication policy, and category fields.
- A software developer starting a local Codex plugin can generate its initial directory and manifest.
- A plugin developer adding scripts, assets, MCP, or app configuration can create optional companion structures in one command.
- A repository maintainer publishing plugins in Codex UI ordering can generate marketplace entries with the required metadata.
- A user managing a home-local plugin can specify a custom plugin parent directory and marketplace path.
Pros & cons
- Creates the required plugin manifest and baseline directory structure.
- Normalizes plugin names and supports multiple optional components.
- Maintains marketplace installation, authentication, category, and ordering metadata.
- Targets the Codex plugin format, so other platforms may require adaptation.
- Generated manifest values remain placeholders and require human completion.
- The source provides no test suite, platform compatibility tests, or detailed failure-handling guidance.
- The README explicitly marks the repository as deprecated.
How to install
The README states that .system skills are automatically installed with the latest Codex. The repository is deprecated, and the README directs users to the OpenAI Plugins repository for current examples. The source does not provide a separate installation command for this skill.
How to use
From the repository root, run python3 .agents/skills/plugin-creator/scripts/create_basic_plugin.py <plugin-name>, then edit the generated .codex-plugin/plugin.json. Add --with-marketplace when a marketplace entry is needed; add --with-skills, --with-hooks, --with-scripts, --with-assets, --with-mcp, or --with-apps for optional structures. If the plugin location is unspecified, choose repo-local or home-local before generating marketplace entries.