plugin-creator

Create and scaffold Codex plugin directories and plugin.json manifests.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill removes the repetitive manual work of creating plugin folders, composing plugin manifests, and updating marketplace catalogs so developers can rapidly produce consistent local plugins for Codex.

Core Features & Use Cases

  • Plugin scaffold generation: Creates a normalized plugin folder with a required .codex-plugin/plugin.json populated with full interface placeholders.
  • Optional companion structures: Can create skills/, hooks/, scripts/, assets/, .mcp.json, and .app.json when requested.
  • Marketplace management: Creates or updates .agents/plugins/marketplace.json entries with explicit installation and authentication policies and preserves displayName when present.
  • Use Case: Useful for repository maintainers or individual developers who need to add new local plugins with consistent manifests and marketplace ordering without hand-editing JSON.

Quick Start

Run the plugin-creator to scaffold a new plugin named my-plugin and optionally add a marketplace entry.

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 new Codex plugin with a plugin.json manifest?

Scaffold a Codex plugin by generating a normalized directory containing a .codex-plugin/plugin.json file populated with full interface placeholders, optionally adding skills, hooks, scripts, and assets subdirectories.

What are the naming requirements for a Codex plugin directory?

Codex plugin directories require normalized kebab-case names with a maximum length of 64 characters to ensure compatibility with the marketplace and local plugin workflows.

How do I add a new plugin entry to the Codex marketplace.json file?

Update the Codex marketplace.json file by appending or overwriting entries with specified installation and authentication policies, preserving the existing displayName when present.

Can I create optional companion directories like hooks and scripts alongside my plugin manifest?

Yes, you can create optional companion directories including skills, hooks, scripts, assets, .mcp.json, and .app.json alongside the core plugin.json manifest during scaffolding.

Does the Codex plugin scaffolding process work for both repo-local and home-local workflows?

Yes, the plugin scaffolding process applies to both repository-local and home-local plugin workflows when adding plugin.json manifests and updating the marketplace catalog.