plugin-creator

Scaffold Codex plugin directories with plugin.json manifests and marketplace.json entries.

Updated Apr 1, 2026
One-click install
npx skills add https://github.com/zniihgnexy/vid_tokenizer --skill plugin-creator-zniihgnexy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plugin-creator
Source: https://github.com/zniihgnexy/vid_tokenizer/tree/main/.ds/codex-home/skills/.system/plugin-creator
Command: npx skills add https://github.com/zniihgnexy/vid_tokenizer --skill plugin-creator-zniihgnexy

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 manifest structure (.codex-plugin/plugin.json), normalized naming rules, and correctly formatted marketplace entries with policy fields. Doing this by hand is error-prone and easy to get wrong. ## Core Features & Use Cases - Plugin Scaffolding: Generates a plugin root with a complete placeholder plugin.json manifest including the full interface section, plus optional skills/, hooks/, scripts/, assets/, .mcp.json, and .app.json structure. - Marketplace Management: Creates or updates .agents/plugins/marketplace.json entries with required policy.installation, policy.authentication, and category fields, supporting both repo-local and home-local plugin locations. - Name Normalization: Converts arbitrary plugin names to lower-case hyphen-case (max 64 chars) so folder names and manifest names always match. - Use Case: You want to publish a new local plugin for Codex. Run the scaffold script with --with-marketplace to get a ready-to-edit plugin skeleton and a valid marketplace entry in one step. ## Quick Start Ask the assistant to scaffold a new plugin named my-plugin with marketplace registration using the plugin-creator skill.

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 create_basic_plugin.py script with your plugin name to generate a plugin folder containing .codex-plugin/plugin.json with placeholder values. Add --with-marketplace to also register the plugin in .agents/plugins/marketplace.json.

How to add a plugin to marketplace.json for Codex?▼

Use the scaffold script with the --with-marketplace flag, which creates or updates .agents/plugins/marketplace.json with an entry containing source path, policy.installation, policy.authentication, and category. Use --force only when intentionally replacing an existing entry.

What fields are required in a Codex plugin.json manifest?▼

The manifest requires a name matching the plugin folder, plus version, description, author, and an interface object with displayName, descriptions, category, capabilities, and asset paths. The scaffold fills all fields with [TODO: ...] placeholders for manual editing.

Can I create a home-local plugin instead of a repo-local one?▼

Yes. Pass --path ~/plugins and --marketplace-path ~/.agents/plugins/marketplace.json to the scaffold script. The marketplace entry still uses the relative path ./plugins/<plugin-name>, which resolves to ~/plugins/<plugin-name>.

What are the allowed policy values in marketplace.json entries?▼

policy.installation accepts NOT_AVAILABLE, AVAILABLE, or INSTALLED_BY_DEFAULT, defaulting to AVAILABLE. policy.authentication accepts ON_INSTALL or ON_USE, defaulting to ON_INSTALL. policy.products is optional and should be omitted unless product gating is explicitly requested.