plugin-creator

Scaffold Better Codex plugin directories with manifests and marketplace entries.

5|1|Updated Jun 26, 2026
One-click install
npx skills add https://github.com/looooonk/better-codex --skill plugin-creator-looooonk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plugin-creator
Source: https://github.com/looooonk/better-codex/tree/main/codex-rs/skills/src/assets/samples/plugin-creator
Command: npx skills add https://github.com/looooonk/better-codex --skill plugin-creator-looooonk

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Creating a Better Codex plugin by hand requires knowing the exact .codex-plugin/plugin.json schema, marketplace.json entry shape, and policy defaults, and mistakes cause ingestion or validation failures. This Skill scaffolds a valid plugin directory, generates marketplace entries with correct defaults, and validates the result before handoff. ## Core Features & Use Cases - Plugin Scaffolding: Generates a normalized plugin folder with a validation-ready plugin.json, plus optional skills/, hooks/, scripts/, assets/, .mcp.json, and .app.json companions. - Marketplace Management: Creates or updates personal (~/.agents/plugins/marketplace.json) or repo/team marketplace entries with required policy.installation, policy.authentication, and category fields. - Update & Validation Flow: Rewrites plugin versions with a codex. cachebuster suffix for local reinstall loops and runs a validator mirroring the ingestion schema. - Use Case: Ask for a new personal plugin named "My Notes" and receive a scaffolded ~/plugins/my-notes/ directory, a marketplace entry, validation results, and Codex app deeplinks to view or share it. ## Quick Start Ask the assistant to create a new Better Codex 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 Better Codex plugin?▼

Run the scaffold script with a plugin name, for example `python3 scripts/create_basic_plugin.py my-plugin`. It creates `~/plugins/my-plugin/.codex-plugin/plugin.json` with valid defaults, and adding `--with-marketplace` also registers it in the personal marketplace file.

How do I add a plugin to the Better Codex marketplace?▼

Pass `--with-marketplace` to the scaffold script to create or update `~/.agents/plugins/marketplace.json`. Each entry includes source path, `policy.installation`, `policy.authentication`, and category, defaulting to AVAILABLE and ON_INSTALL.

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

Run `scripts/update_plugin_cachebuster.py <plugin-path>` to rewrite the version with a `codex.` cachebuster suffix, then reinstall with `better-codex plugin add <plugin-name>@<marketplace-name>`. Start a new thread afterward so Better Codex picks up the updated plugin.

What fields does plugin.json validation require?▼

The validator requires non-empty `name`, strict semver `version`, `description`, `author.name`, and an `interface` object with displayName, shortDescription, longDescription, developerName, category, capabilities, and a defaultPrompt. Unsupported fields like `hooks` are rejected.

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

Use a repo/team marketplace only when the user explicitly requests that destination, by passing `--path` and `--marketplace-path` pointing into the repo. Non-default marketplaces must be installed with `better-codex plugin marketplace add` before reinstalling from them.