plugin-creator

Scaffold and validate Codex plugin directories, manifests, and marketplace entries.

Updated May 28, 2026

Search Tags:#validation #scaffolding #codex #plugin #manifest #marketplace

Ready to run

npx skills add https://github.com/haryelramalho/skills --skill plugin-creator-haryelramalho

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plugin-creator
Source: https://github.com/haryelramalho/skills/tree/main/skills/community/plugin-creator
Command: npx skills add https://github.com/haryelramalho/skills --skill plugin-creator-haryelramalho

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill removes the manual work of creating Codex plugin scaffolds, keeping the manifest, companion files, and marketplace entry aligned from the start.

Core Features & Use Cases

Plugin Scaffolding: Creates a normalized plugin folder with a valid .codex-plugin/plugin.json and optional companion directories.
Marketplace Management: Adds or updates personal marketplace entries with the correct source path, policy values, and ordering.
Safe Iteration: Supports local development updates with cachebuster refreshes and validation before handoff.
Use Case: A developer can turn a rough plugin idea into a ready-to-install local plugin without hand-editing manifest boilerplate.

Quick Start

Ask the assistant to scaffold a new plugin with your chosen name and metadata, then validate the generated plugin before sharing it.

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 directory with a valid manifest?▼

You can scaffold a Codex plugin by providing a normalized plugin name, which generates the required .codex-plugin/plugin.json manifest and optional companion directories like .mcp.json and .app.json automatically.

What is included in Codex plugin scaffolding?▼

Codex plugin scaffolding includes creating a normalized plugin directory with a valid .codex-plugin/plugin.json manifest. It also supports optional companion folders like .mcp.json and .app.json, and validates strict manifest fields during the generation process.

How do I publish a plugin to a personal Codex marketplace?▼

Publishing to a personal Codex marketplace involves adding or updating marketplace entries with the correct source path and policy values. The scaffolding process manages entry ordering and ensures manifest alignment before publishing.

Do I need PyYAML to validate Codex plugin manifests?▼

Yes, PyYAML is required to validate Codex plugin manifests. The validation process uses PyYAML-backed skill frontmatter validation to ensure your .codex-plugin/plugin.json and companion files meet strict manifest field requirements.

Can I refresh local Codex plugin development files without breaking the manifest?▼

You can refresh local Codex plugin development files safely using cachebuster refreshes. The process validates your plugin directory and companion files before handoff, ensuring the manifest remains aligned during local development updates.

What are the limitations when creating Codex plugin companion folders?▼

Creating Codex plugin companion folders requires strict adherence to manifest field rules. You must maintain a valid .codex-plugin/plugin.json, and optional .mcp.json or .app.json companions must align with the normalized plugin name to pass validation.