Scaffold Codex plugin directories with manifests and marketplace entries.
npx skills add https://github.com/chhpt/skills --skill plugin-creator-chhpt
Please help me install this Agent Skill. Skill: plugin-creator Source: https://github.com/chhpt/skills/tree/main/skills/plugin-creator Command: npx skills add https://github.com/chhpt/skills --skill plugin-creator-chhpt
.codex-plugin/plugin.json manifest schema, naming rules, and marketplace entry policies exactly right, and mistakes cause ingestion or validation failures. This Skill scaffolds valid plugin directories and marketplace entries with correct defaults so plugins pass validation on the first attempt. ## Core Features & Use Cases - Plugin Scaffolding: Generates a normalized plugin folder with a validation-ready plugin.json, plus optional skills/, hooks/, scripts/, assets/, .mcp.json, and .app.json companions. - Marketplace Management: Creates or updates personal or repo/team marketplace.json files with correct policy, category, and source path entries. - Update & Validation Flow: Rewrites plugin versions with a Codex cachebuster suffix for reinstall during local development, and validates manifests against the ingestion contract. - Use Case: Ask Codex to create a new personal plugin named "My Tools"; the Skill normalizes the name to my-tools, scaffolds the plugin under ~/plugins, adds a personal marketplace entry, and validates the result before handing it back. ## Quick Start Ask Codex to create a new personal plugin named my-plugin with a marketplace entry and validate it before handing it back.High-intent search queries and answers about installing and using this skill.
Run the scaffold script with a plugin name to generate the plugin folder and a valid `.codex-plugin/plugin.json` manifest. Add `--with-marketplace` to also create or update the personal marketplace entry at `~/.agents/plugins/marketplace.json`.
Use the scaffold script with `--with-marketplace` to append an entry containing source path, installation policy, authentication policy, and category. New entries default to the personal marketplace file and are appended in render order.
Run the cachebuster update script on the plugin path to rewrite the version with a `+codex.<timestamp>` suffix, then reinstall with `codex plugin add <plugin-name>@<marketplace-name>`. Start a new thread afterward so Codex picks up the updated plugin.
The manifest requires non-empty `name`, strict semver `version`, `description`, `author.name`, and an `interface` object with displayName, shortDescription, longDescription, developerName, category, capabilities, and defaultPrompt. Unsupported fields like `hooks` are rejected by validation.
Validation fails on leftover `[TODO: ...]` placeholders, non-semver versions, unsupported manifest fields, non-HTTPS URLs, or asset paths pointing to missing files. Run `validate_plugin.py` on the plugin path to list every specific error.
Use a repo/team marketplace only when the user explicitly requests that destination, passing both `--path` and `--marketplace-path`. Non-default marketplaces must be installed with `codex plugin marketplace add` before reinstalling plugins from them.
ayubunGuide developers in creating opencode plugins with structured directories and plugin.json manifests.
rjschieAutomate Codex plugin creation and management via CLI commands.
christophevgScaffold Claude Code plugin structures with skills, agents, hooks, and MCP servers.
am-willInstalls Codex plugins from GitHub repos into repo or personal marketplaces.