plugin-creator

Scaffolding a plugin pack for Claude or Codex runtimes involves generating a plugin.json manifest, README, and optional subdirectories for agents, skills, hooks, and templates. The process enforces manifest structure and references assets for repeatable plugin packaging.

An opt-in plugin pack is a structured bundle of domain-specific plugins with manifests and assets for safe deployment. You need one when packaging plugins for Claude and Codex runtimes to ensure consistent structure, validation, and clear documentation.

Yes, you can include custom assets like hooks and templates when creating a plugin manifest. The scaffolding process supports optional subdirectories for agents, skills, hooks, and templates, and the manifest template includes fields for referencing included assets.

The best way to structure an experimental plugin for domain-specific use is using a scaffolded pack with predefined manifest fields for name, description, version, domain, and compatibility. This ensures validation workflows and clear documentation for safe deployment.

No external dependencies are required to generate plugin scaffolds and manifests. The workflow operates independently to enforce manifest structure, reference assets, and document the opt-in workflow for repeatable plugin packaging.

Limitations when packaging experimental plugins include enforcing strict manifest structure and compatibility fields for Claude and Codex runtimes. The opt-in workflow prioritizes safe, repeatable packaging, meaning plugins must pass validation before deployment.