plugin-creator

Scaffold Codex plugin directories with validated manifests and marketplace entries.

Updated Dec 20, 2025
One-click install
npx skills add https://github.com/koala-man-64/helpful-scripts --skill plugin-creator-koala-man-64
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plugin-creator
Source: https://github.com/koala-man-64/helpful-scripts/tree/main/exports/codex-skills/home-shared/.system/plugin-creator
Command: npx skills add https://github.com/koala-man-64/helpful-scripts --skill plugin-creator-koala-man-64

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 entry policies exactly right, and mistakes cause ingestion or validation failures. This Skill scaffolds compliant plugin directories and marketplace entries so generated plugins pass validation on the first attempt. ## 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 files with correct policy, category, and source path entries. - Validation & Update Loop: Validates generated plugins against the ingestion contract and rewrites version cachebusters for the local reinstall workflow. - Use Case: Ask the assistant to create a new personal Codex plugin named "my-reports"; it scaffolds the plugin, registers it in the personal marketplace, validates it, and returns Codex app deeplinks. ## Quick Start Ask the assistant to create a new Codex plugin with a given name and have it scaffolded, registered in the personal marketplace, and validated.

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 scaffold script with a plugin name to generate the plugin folder and a valid `.codex-plugin/plugin.json` manifest. Add `--with-marketplace` to also register it in the personal marketplace at `~/.agents/plugins/marketplace.json`.

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

Run the cachebuster update script against 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.

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

The manifest requires non-empty `name`, strict semver `version`, `description`, an `author` object with `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?▼

Common causes are leftover `[TODO: ...]` placeholders, non-semver versions, missing interface fields, non-HTTPS URLs, or asset paths pointing outside the plugin archive. Run `scripts/validate_plugin.py <plugin-path>` to list every violation.

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

Use a repo or team marketplace only when explicitly requested, by passing both `--path` and `--marketplace-path`. Non-default marketplaces are not discovered implicitly, so they must be installed with `codex plugin marketplace add` before reinstalling plugins from them.