skills.rest
ebijun1007
ebijun1007COMMUNITY
Explore all skills by this author →
GitHub

plugin-creator

Scaffold Codex plugin directories with manifest and marketplace entries.

Updated Aug 23, 2026
Search Tags:#automation#cli#codex#scaffold#plugin#marketplace#skeleton
One-click install
npx skills add https://github.com/ebijun1007/vibe-coding --skill plugin-creator-ebijun1007
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plugin-creator
Source: https://github.com/ebijun1007/vibe-coding/tree/main/.codex/skills/.system/plugin-creator
Command: npx skills add https://github.com/ebijun1007/vibe-coding --skill plugin-creator-ebijun1007

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Create and scaffold Codex plugin directories and marketplace entries from a single command, reducing boilerplate and ensuring consistent structure.

Core Features & Use Cases

  • Scaffold plugin root at <parent>/<plugin-name> with .codex-plugin/plugin.json skeleton.
  • Optional directories: skills/, hooks/, scripts/, assets/ plus placeholders (.mcp.json, .app.json).
  • Generate or update <repo>/.agents/plugins/marketplace.json with a standard marketplace entry pointing to ./plugins/<plugin-name>.
  • Validate plugin name normalization and maintain compatibility with repository conventions.

Quick Start

Run the scaffold script from the repository root to generate the plugin skeleton.

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

Scaffolding a Codex plugin generates a ready-to-edit plugin manifest at .codex-plugin/plugin.json along with optional skeleton directories for skills, hooks, scripts, and assets, reducing boilerplate by automating directory creation.

Can I generate a marketplace entry when creating a new Codex plugin?▼

Yes, you can generate a marketplace entry by requesting it during scaffolding, which creates or updates your repository's marketplace.json file with a standard entry pointing to ./plugins/<plugin-name>.

What is the standard directory structure for a Codex plugin?▼

The standard Codex plugin structure uses a root at plugins/<plugin-name> containing a .codex-plugin/plugin.json manifest, alongside optional folders for skills, hooks, scripts, assets, and placeholder files like .mcp.json and .app.json.

Does the plugin scaffolder enforce naming conventions for Codex plugins?▼

Yes, the scaffolder enforces plugin-name normalization to ensure compatibility with repository conventions, validating names and maintaining deterministic manifest structures when generating the plugin root.

Can I overwrite existing plugin files when scaffolding a Codex plugin?▼

Yes, you can use specific flags to force overwrites of existing files when scaffolding your Codex plugin, allowing you to regenerate manifests and directory structures without manual deletion.

Where should I place the plugin root when scaffolding a Codex plugin?▼

You can place the plugin root at a repo-local or home-local path under plugins/<plugin-name>, allowing flexible plugin organization while maintaining consistent path conventions for your Codex setup.

Related Skills

Explore More Software Engineering Skills→
bingran-youbingran-you
3

plugin-creator

Scaffold Codex plugin directories with .codex-plugin/plugin.json and optional folders.

Community
Intermediate
erichugyerichugy

plugin-creator

Create and scaffold Codex plugin directories and plugin.json manifests.

Community
Intermediate
ammonfifeammonfife

plugin-creator

Automate Codex plugin directory creation and marketplace entry management.

Community
Advanced
haryelramalhoharyelramalho

plugin-creator

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

Community
Advanced