plugin-creator

Scaffold Codex plugin directories, plugin.json skeletons, and marketplace entries.

Updated Sep 6, 2025
One-click install
npx skills add https://github.com/yyoonchul/agent-rules --skill plugin-creator-yyoonchul
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plugin-creator
Source: https://github.com/yyoonchul/agent-rules/tree/main/agent-skills/skills/.system/plugin-creator
Command: npx skills add https://github.com/yyoonchul/agent-rules --skill plugin-creator-yyoonchul

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This tool streamlines the process of scaffolding Codex plugins by generating a ready-to-edit plugin skeleton and marketplace entry, reducing setup time and ensuring consistency.

Core Features & Use Cases

  • Scaffold a new plugin directory with a placeholder .codex-plugin/plugin.json and optional folders (skills, hooks, scripts, assets).
  • Generate or update the top-level marketplace entry with relative plugin paths, preserving existing marketplace interface.displayName.
  • Produce placeholder files for optional components and marketplace metadata to be completed later.

Quick Start

Run the scaffold script to create a new plugin skeleton at <repo_root>/plugins/<plugin-name> and optionally update the marketplace.

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 skeleton with the correct directory structure?

To scaffold a Codex plugin, run the script to generate a ready-to-edit directory with a placeholder .codex-plugin/plugin.json and optional folders like skills, hooks, scripts, and assets, ensuring standardized plugin development and reduced setup time.

What is the process to update marketplace.json entries with relative plugin paths?

Updating marketplace.json involves generating or updating the top-level marketplace entry with relative plugin paths while preserving any existing marketplace interface.displayName, ensuring correct marketplace integration for repo-based plugins.

Does the plugin scaffolding process support both local and repo-based plugins?

Yes, the scaffolding process supports developers creating both local plugins and repo-based plugins by enforcing the plugin.json skeleton and handling directory creation and marketplace metadata updates with relative paths.

Can I generate placeholder files for optional plugin components like hooks and scripts?

Yes, you can generate placeholder files for optional plugin components such as hooks, scripts, skills, and assets, allowing you to complete the specific marketplace metadata and component logic later without initial setup friction.

What is the best way to standardize Codex plugin development across multiple projects?

The best way to standardize Codex plugin development is to use a scaffolding tool that enforces the plugin.json skeleton, automates optional component folder creation, and integrates marketplace.json entries, ensuring consistency across projects.