plugin-creator

Scaffold Codex plugin directories with validated manifests and marketplace entries.

1|Updated Aug 1, 2026
One-click install
npx skills add https://github.com/xlnn/modelmux-vscode --skill plugin-creator-xlnn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plugin-creator
Source: https://github.com/xlnn/modelmux-vscode/tree/main/.tmp-codex-home4/skills/.system/plugin-creator
Command: npx skills add https://github.com/xlnn/modelmux-vscode --skill plugin-creator-xlnn

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, marketplace entry policies, and naming rules exactly right, and mistakes cause ingestion or validation failures. This Skill automates scaffolding, marketplace registration, and validation so plugins conform to the expected contract from the start. ## Core Features & Use Cases - Plugin Scaffolding: Generates a normalized plugin directory with a valid plugin.json, optional skills/, hooks/, scripts/, assets/ folders, and .mcp.json or .app.json companion files. - Marketplace Management: Creates or updates personal or repo/team marketplace.json entries with correct policy, category, and source path fields. - Validation and Update Flow: Validates generated plugins against the ingestion schema and rewrites version cachebusters for the local reinstall loop during development. - Use Case: Ask Codex to create a new personal plugin named "my-tools"; the Skill scaffolds the folder, seeds the personal marketplace entry, validates the manifest, and returns View and 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 from scratch?

Run the create_basic_plugin.py script with a plugin name to scaffold the directory, manifest, and optional folders. Add --with-marketplace to also register the plugin in the personal marketplace file at ~/.agents/plugins/marketplace.json.

How do I add a plugin to the Codex marketplace?

Pass --with-marketplace when scaffolding to create or update the marketplace.json entry with policy.installation, policy.authentication, and category fields. New entries default to AVAILABLE and ON_INSTALL, appended in render order.

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.

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

Run update_plugin_cachebuster.py on the 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 manifest?

Validation fails for leftover [TODO: ...] placeholders, non-semver versions, missing required interface fields, non-https URLs, or asset paths pointing outside the plugin archive. Run scripts/validate_plugin.py to list every specific error.