plugin-creator

Scaffold Codex plugin directories and generate placeholder plugin.json manifests.

5.0k|682|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/openai/plugins --skill plugin-creator-openai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plugin-creator
Source: https://github.com/openai/plugins/tree/main/.agents/skills/plugin-creator
Command: npx skills add https://github.com/openai/plugins --skill plugin-creator-openai

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Rapidly creating a correctly structured plugin folder and manifest is error-prone and repetitive; this Skill eliminates manual manifest scaffolding and naming inconsistencies so developers can start implementing functionality immediately.

Core Features & Use Cases

  • Automatic Manifest Generation: Writes a full .codex-plugin/plugin.json manifest prefilled with the complete interface schema and placeholder values for quick editing.
  • Name Normalization & Validation: Normalizes plugin names to lowercase hyphen-case, collapses duplicate hyphens, and enforces a 64-character limit to meet naming rules.
  • Optional Component Stubs: Can create companion directories and stubs for skills, hooks, scripts, assets, .mcp.json, and .app.json to scaffold common plugin components for testing and development.
  • Use Case: Use this Skill to quickly scaffold a fresh Codex plugin skeleton before iterating on implementation and documentation.

Quick Start

Run the plugin-creator script to scaffold a new plugin named my-plugin in the repository plugins directory and then edit the generated .codex-plugin/plugin.json placeholders.

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 manifest and directory structure?

To scaffold a Codex plugin, run the plugin-creator script to automatically generate a normalized plugin folder containing a .codex-plugin/plugin.json manifest and optional companion directories for skills, hooks, and scripts.

What naming rules does a Codex plugin manifest require for the plugin directory?

A Codex plugin manifest requires lowercase hyphen-case naming with a 64-character limit. The scaffolding process automatically normalizes names, collapses duplicate hyphens, and enforces these rules to prevent naming inconsistencies.

Can I generate stub files for hooks, assets, and MCP servers when creating a plugin?

Yes, you can generate optional component stubs for hooks, assets, scripts, skills, .mcp.json, and .app.json when scaffolding a plugin, providing companion directories ready for local testing and development.

Does the plugin scaffolding process overwrite existing files in the plugin folder?

The plugin scaffolding process provides idempotent file creation, meaning it safely skips existing files by default. You can use an optional force overwrite flag to replace existing manifest or component stub files.

What is the best way to automate creating multiple plugin.json manifests for local testing?

Automating plugin manifest creation is best handled by running the scaffolding script, which writes complete interface schemas with placeholder values into .codex-plugin/plugin.json files, allowing rapid iteration across multiple plugin projects.