plugin-creator

Scaffold Codex plugin directories with validated manifests and marketplace entries.

Updated Jul 31, 2026
One-click install
npx skills add https://github.com/AarnavBaddam/skills --skill plugin-creator-aarnavbaddam
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plugin-creator
Source: https://github.com/AarnavBaddam/skills/tree/main/.system/plugin-creator
Command: npx skills add https://github.com/AarnavBaddam/skills --skill plugin-creator-aarnavbaddam

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Creating a Codex plugin by hand requires getting the .codex-plugin/plugin.json manifest schema, naming rules, and marketplace.json entry shape exactly right, and mistakes cause ingestion or validation failures. This Skill scaffolds compliant plugins and marketplace entries automatically. ## Core Features & Use Cases - Plugin Scaffolding: Generates a normalized plugin directory with a validation-ready plugin.json, plus optional skills/, hooks/, scripts/, assets/, .mcp.json, and .app.json companions. - Marketplace Management: Creates or updates personal or repo/team marketplace.json files with correct policy, category, and source path fields. - Update & Validation Flow: Rewrites plugin versions with a Codex cachebuster suffix for reinstall-driven iteration and validates manifests against the ingestion contract. - Use Case: Ask Codex to create a new personal plugin named "My Reports"; the Skill normalizes the name to my-reports, scaffolds it under ~/plugins, registers it in the personal marketplace, and validates the result before handing it back. ## Quick Start Ask Codex to create a new plugin named my-plugin in the personal marketplace and validate it before finishing.

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?

Run the scaffold script with a plugin name, for example `python3 scripts/create_basic_plugin.py my-plugin`. It creates the plugin folder under `~/plugins`, writes a valid `.codex-plugin/plugin.json`, and can register the plugin in the personal marketplace with `--with-marketplace`.

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

Pass `--with-marketplace` to the scaffold script, which creates or updates `~/.agents/plugins/marketplace.json` by default. Each entry includes the plugin name, a local source path of `./plugins/<plugin-name>`, installation and authentication policies, and a category.

How do I update an existing local Codex plugin during development?

Run `update_plugin_cachebuster.py <plugin-path>` to rewrite the version with a `+codex.<timestamp>` suffix, then reinstall with `codex plugin add <plugin-name>@<marketplace-name>`. Start a new thread afterward so Codex picks up the updated skills and tools.

Why does Codex plugin validation fail on my plugin.json?

Validation rejects leftover `[TODO: ...]` placeholders, non-semver versions, unsupported fields like `hooks`, missing required interface fields, and asset paths pointing to files that do not exist. Run `validate_plugin.py <plugin-path>` to list every specific error.

What naming rules apply to Codex plugin names?

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