plugin-creator

Scaffold Codex plugin directories with manifest placeholders and marketplace.json entries.

5|1|Updated May 5, 2026
One-click install
npx skills add https://github.com/cbusillo/codex-skills --skill plugin-creator-cbusillo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plugin-creator
Source: https://github.com/cbusillo/codex-skills/tree/main/skills/plugin-creator
Command: npx skills add https://github.com/cbusillo/codex-skills --skill plugin-creator-cbusillo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Creating a new Codex plugin requires a specific directory layout, a .codex-plugin/plugin.json manifest with the full schema shape, and optionally a correctly formatted marketplace.json entry; doing this by hand is error-prone and easy to get wrong. ## Core Features & Use Cases - Plugin Scaffolding: Generates a plugin directory with a normalized kebab-case name and a complete placeholder plugin.json including the full interface section. - Optional Structure: Adds skills/, hooks/, scripts/, assets/, .mcp.json, and .app.json on demand via flags. - Marketplace Management: Creates or updates .agents/plugins/marketplace.json entries with required policy.installation, policy.authentication, and category fields, preserving existing interface.displayName. - Use Case: You want to publish a new local plugin called "Linear Sync" for Codex; run the scaffold script to get plugins/linear-sync/ with a placeholder manifest and a marketplace entry ready to edit. ## Quick Start Ask the agent to create a new Codex plugin named my-plugin with a marketplace entry using the plugin-creator scaffold script.

Frequently Asked Questions about plugin-creator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a new Codex plugin scaffold?

Run the create_basic_plugin.py script with a plugin name, for example `uv run scripts/create_basic_plugin.py my-plugin`. It creates `plugins/my-plugin/.codex-plugin/plugin.json` filled with placeholder values you replace before publishing.

How do I add a plugin to the Codex marketplace.json?

Pass the `--with-marketplace` flag when scaffolding. The script creates or updates `.agents/plugins/marketplace.json` at the repo root (or `~/.agents/plugins/marketplace.json` for home-local plugins) with an entry containing policy.installation, policy.authentication, and category.

What naming rules apply to Codex plugin names?

Plugin names are normalized to lower-case hyphen-case: spaces, underscores, and punctuation become hyphens, consecutive hyphens collapse, and the result must be 64 characters or fewer. The folder name and plugin.json name always match.

Can I add skills, hooks, or MCP config to a plugin scaffold?

Yes, use the flags `--with-skills`, `--with-hooks`, `--with-scripts`, `--with-assets`, `--with-mcp`, and `--with-apps`. These create the corresponding directories or stub `.mcp.json` and `.app.json` files inside the plugin root.

What happens if a marketplace entry for the plugin already exists?

The script raises an error and refuses to overwrite the existing entry unless you pass `--force`. Without `--force`, existing files and marketplace entries are preserved to prevent accidental replacement.