plugin-creator

Scaffold Codex plugin projects with placeholder configurations and marketplace.json integration.

1|Updated Feb 24, 2026
One-click install
npx skills add https://github.com/dzackgarza/ai --skill plugin-creator-dzackgarza
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plugin-creator
Source: https://github.com/dzackgarza/ai/tree/main/opencode/skills/.system/plugin-creator
Command: npx skills add https://github.com/dzackgarza/ai --skill plugin-creator-dzackgarza

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Create and scaffold plugin directories for Codex 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

  • Scaffold plugin root at the project root with a default .codex-plugin/plugin.json containing placeholders.
  • Generate optional directories: skills/, hooks/, scripts/, assets/.
  • Update or create marketplace entries at the specified marketplace path with relative plugin paths: ./plugins/<plugin-name> and default policies.
  • Create optional placeholders for .mcp.json and .app.json when requested by flags (for example, --with-mcp and --with-apps).

Quick Start

From the repository root, run the scaffold script to generate a new plugin with 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 the correct directory structure?▼

Scaffolding a Codex plugin generates a project root with a default .codex-plugin/plugin.json file and optional directories like skills/, hooks/, scripts/, and assets/ populated with editable placeholder configurations.

What is a .codex-plugin/plugin.json file and when do I need to create one?▼

A .codex-plugin/plugin.json file is a required configuration containing baseline metadata and placeholders for a Codex plugin. You need to create one whenever developing a new local plugin for testing or publishing.

How do I add a new plugin to my marketplace.json file for ordering and availability?▼

To add a plugin to marketplace.json, run the scaffolder with a specified path to automatically insert relative plugin paths like ./plugins/<plugin-name> and apply default ordering and availability policies.

Can I generate .mcp.json and .app.json placeholders when creating a new plugin?▼

Yes, you can generate optional .mcp.json and .app.json placeholder files by passing specific flags such as --with-mcp and --with-apps when executing the plugin scaffolding script.

Does the Codex plugin scaffolder validate plugin names and normalize directory paths?▼

Yes, the Codex plugin scaffolder enforces naming normalization and validates plugin names before creating required paths, ensuring your repository-local plugin directory structure remains consistent and correctly formatted.

What are the limitations of using a scaffolder for local plugin development?▼

The scaffolder generates baseline placeholder configurations that you must manually edit before publishing or testing. It handles initial structure creation and marketplace.json integration rather than writing functional plugin logic.