plugin-creator

Scaffold Codex plugin directories with validated manifests and marketplace entries.

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

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 format exactly right, and mistakes cause ingestion or validation failures. This Skill automates scaffolding, validation, and the local update/reinstall loop so plugins conform to the ingestion contract from the start. ## Core Features & Use Cases - Plugin Scaffolding: Generates a normalized plugin folder with a valid plugin.json, optional skills/, hooks/, scripts/, assets/, .mcp.json, and .app.json companions. - Marketplace Management: Creates or updates personal or repo/team marketplace.json entries with correct policy, category, and source path fields. - Validation & Update Loop: Validates generated plugins against the ingestion schema and rewrites version cachebusters for CLI-driven reinstall during development. - Use Case: Ask Codex to create a new personal plugin named "my-tools"; the Skill scaffolds the directory, registers it in the personal marketplace, validates the manifest, and provides View/Share deeplinks for the Codex app. ## Quick Start Ask Codex to create a new plugin named my-plugin in the personal marketplace and validate it before handing it back.

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 a plugin name to scaffold the directory, manifest, and optional folders. Add the --with-marketplace flag to also register the plugin in the personal marketplace at ~/.agents/plugins/marketplace.json.

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

Read the marketplace name with read_marketplace_name.py, bump the version cachebuster with update_plugin_cachebuster.py, then reinstall using codex plugin add <plugin-name>@<marketplace-name>. Start a new thread afterward so Codex picks up the updated skills and tools.

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

The manifest requires name, strict semver version, description, author.name, and an interface object with displayName, shortDescription, longDescription, developerName, category, capabilities, and defaultPrompt. Unsupported fields like hooks are rejected by validation.

Why does Codex plugin validation fail on my manifest?

Validation fails for leftover [TODO: ...] placeholders, non-semver versions, non-https URLs, missing asset files, or unsupported manifest fields. Run validate_plugin.py against the plugin root to list every specific error before handing the plugin back.

When should I use a repo marketplace instead of the personal marketplace?

Use a repo/team marketplace only when the user explicitly requests that destination, passing both --path and --marketplace-path. Non-default marketplaces must be installed with codex plugin marketplace add before reinstall commands work.