plugin-creator

Scaffold Codex plugin skeletons with manifests and marketplace entries.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/jbarlek3-web/claudecommandcenter --skill plugin-creator-jbarlek3-web
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plugin-creator
Source: https://github.com/jbarlek3-web/claudecommandcenter/tree/main/skills/.system/plugin-creator
Command: npx skills add https://github.com/jbarlek3-web/claudecommandcenter --skill plugin-creator-jbarlek3-web

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Create and scaffold Codex plugin directories with a required .codex-plugin/plugin.json, optional plugin folders/files, and baseline placeholders you can edit before publishing or testing. Use when Codex needs to create a new local plugin, add optional plugin structure, or generate or update repo-root .agents/plugins/marketplace.json entries for plugin ordering and availability metadata.

Core Features & Use Cases

  • Automatically generate a plugin skeleton including .codex-plugin/plugin.json and placeholder fields.
  • Create optional directories (skills, hooks, scripts, assets) and placeholder files (mcp.json, app.json) as needed.
  • Update the marketplace.json to register the new plugin and establish repository/local discovery metadata.

Quick Start

Run the create_basic_plugin.py script with your plugin name to generate a skeleton and placeholder files.

Frequently Asked Questions about plugin-creator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I scaffold a Codex plugin with a standardized manifest?

To scaffold a Codex plugin, run the creation script with your plugin name to generate a skeleton directory, including the required .codex-plugin/plugin.json manifest and placeholder fields for immediate editing.

What is the best way to generate marketplace entries for local Codex plugins?

Generating marketplace entries is handled by updating the repo-root marketplace.json file, which registers new plugins and establishes repository discovery metadata and ordering for local availability.

Does the plugin scaffolding process support optional directories like skills and hooks?

Yes, plugin scaffolding supports creating optional subdirectories such as skills, hooks, scripts, and assets, along with placeholder files like mcp.json and app.json as needed for your structure.

Can I update existing plugin manifests without overwriting my current files?

Yes, you can update manifests safely because the scaffolding process preserves existing files during creation or updates unless you explicitly use an overwrite flag to replace them.

Are there naming restrictions when creating a Codex plugin skeleton?

Yes, creating a Codex plugin skeleton enforces strict naming rules and validates length constraints to ensure the plugin name meets standardized manifest requirements before writing any files.