plugin-creator

Generate Codex plugin scaffolds with manifests and marketplace entries.

Updated Jul 10, 2023

Search Tags:#automation #template #codex #scaffold #plugin #marketplace

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Scaffold Codex plugin projects by generating a skeleton plugin manifest, optional directories, and marketplace entries to accelerate plugin development workflows.

Core Features & Use Cases

Scaffold plugin root and a minimal .codex-plugin/plugin.json with placeholder fields.
Create optional plugin structures: skills/, hooks/, scripts/, assets/, .mcp.json, .app.json.
Update or generate marketplace.json so plugins appear in the Codex UI and are properly linked to ./plugins/<plugin-name>.
Normalize plugin names to kebab-case and enforce size limits for consistency.
Use cases include starting a repo-local plugin, adding a home-local plugin, or updating the marketplace after plugin creation.

Quick Start

Run the scaffold script from the repository root with your chosen plugin name.

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

To scaffold a Codex plugin, run the scaffold script from the repository root with your chosen name to generate a minimal .codex-plugin/plugin.json manifest and optional directories.

How do I add a new plugin to the Codex marketplace?▼

Adding a plugin to the Codex marketplace involves generating or updating the marketplace.json file, which links your new plugin to ./plugins/<plugin-name> so it appears in the UI.

What is the required naming format for a Codex plugin?▼

The required naming format for a Codex plugin is kebab-case. The scaffold process normalizes plugin names to kebab-case and enforces size limits to maintain marketplace consistency.

What optional directories can I create when scaffolding a Codex plugin?▼

When scaffolding a Codex plugin, you can create optional structures including skills/, hooks/, scripts/, assets/, .mcp.json, and .app.json directories alongside the root manifest.

Do I need any external dependencies to scaffold a Codex plugin?▼

No external dependencies are required to scaffold a Codex plugin. The skill operates independently using internal scripts to generate the placeholder manifest and marketplace entries.

Can I use this scaffold to update an existing marketplace entry?▼

Yes, you can use the scaffold to update an existing marketplace entry. It safely generates or updates the marketplace.json file to ensure plugins remain properly linked and visible.