plugin-creator

Scaffold Codex plugins with a plugin.json manifest and optional directories.

1|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/sss-hust/skills --skill plugin-creator-sss-hust
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plugin-creator
Source: https://github.com/sss-hust/skills/tree/main/.system/plugin-creator
Command: npx skills add https://github.com/sss-hust/skills --skill plugin-creator-sss-hust

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Streamlines the initial setup of Codex plugins by generating a ready-to-edit plugin manifest and optional scaffolds, reducing boilerplate and setup time.

Core Features & Use Cases

  • Automatically creates plugin root at <repo-root>/plugins/<plugin-name> with a .codex-plugin/plugin.json containing placeholders.
  • Optionally scaffolds directories like skills/, hooks/, scripts/, and assets/ plus placeholders for .mcp.json and .app.json, to align with Codex plugin projects.
  • Updates repo marketplace metadata when requested, using safe defaults and relative paths to keep marketplace in sync.

Quick Start

Run the plugin-creator with a plugin name to scaffold a new plugin and optional skeletons.

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

Scaffolding a Codex plugin generates a ready-to-edit .codex-plugin/plugin.json manifest with placeholders and optional skeletons for skills, hooks, scripts, and assets, ensuring required directories are created with consistent naming normalization.

Can I automatically update marketplace.json when creating a new Codex plugin?

Yes, you can update marketplace.json when scaffolding your Codex plugin. The tool applies safe default policies and relative paths to keep your repository marketplace metadata in sync with newly generated plugin entries.

What optional files and directories can I generate for a Codex plugin project?

When scaffolding Codex plugins, you can optionally generate skills/, hooks/, scripts/, and assets/ directories, along with placeholder files for .mcp.json and .app.json to align with standard Codex plugin project structures.

Does Codex plugin scaffolding support adding local scripts and hooks?

Yes, Codex plugin scaffolding supports adding local scripts and hooks by optionally creating the hooks/ and scripts/ directories, allowing you to populate these skeletons with custom automation and execution logic during local plugin development.

What is the best way to reduce boilerplate when setting up multiple Codex plugins?

The best way to reduce Codex plugin boilerplate is using a scaffolding generator that automatically creates the .codex-plugin/plugin.json manifest with placeholders, normalizes naming, and optionally updates marketplace.json with safe defaults for each new plugin.