plugin-creator

Generate Codex plugin scaffolds with manifests and marketplace registration.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill solves the overhead of creating and standardizing new Codex plugins by generating the required plugin manifest and optional supporting structure so you can publish with consistent metadata.

Core Features & Use Cases

  • Plugin scaffolding: Creates a plugin directory containing a required .codex-plugin/plugin.json manifest with placeholder values you can edit.
  • Optional companion structure: Generates optional folders and placeholder files such as skills/, hooks/, scripts/, assets/, .mcp.json, and .app.json to match what your plugin needs.
  • Marketplace ordering and availability: Generates or updates .agents/plugins/marketplace.json with correct policy fields (installation/authentication), category, and ordering behavior for Codex UI availability.

Quick Start

Use plugin-creator to scaffold a new plugin called my-awesome-plugin by running the scaffold script, then edit the placeholders in .codex-plugin/plugin.json 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 create a Codex plugin manifest for local development?

To create a Codex plugin manifest, generate a standardized scaffold containing the required .codex-plugin/plugin.json file. This manifest includes placeholder values that you edit to define your local tooling while satisfying normalized plugin naming constraints.

What is the directory structure required for scaffolding a Codex plugin?

The required directory structure for scaffolding a Codex plugin includes the .codex-plugin/plugin.json manifest. Optional companion folders and placeholder files like skills/, hooks/, scripts/, assets/, .mcp.json, and .app.json can also be generated to match your specific plugin requirements.

How do I register my Codex plugin in the marketplace.json file?

You register a Codex plugin by creating or updating the .agents/plugins/marketplace.json file. This process involves generating correct policy fields including installation, authentication, and category, while ensuring proper ordering behavior for Codex UI availability.

Does Codex plugin scaffolding support custom policy fields for marketplace availability?

Yes, Codex plugin scaffolding supports custom policy fields for marketplace availability. When generating or updating the .agents/plugins/marketplace.json file, it validates and includes required policy fields such as policy.installation, policy.authentication, and category to ensure correct UI ordering.

Can I generate placeholder files for hooks and scripts when scaffolding a Codex plugin?

Yes, you can generate placeholder files for hooks and scripts. The plugin scaffolding process creates optional companion directories including hooks/, scripts/, skills/, and assets/, allowing you to populate them with placeholder files tailored to your plugin's functionality.

What limitations exist when validating marketplace entries for Codex plugins?

Limitations when validating marketplace entries include strict adherence to normalized plugin naming constraints and placeholder retention requirements. The generation process is validation-oriented, meaning the marketplace.json must have correct policy fields and ordering rules to achieve Codex UI availability.