数据分析

plugin-creator

试用

生成 Codex 插件目录,附带填好结构的 plugin.json 清单和可选的 marketplace 条目。

它能做什么

通过 Python 脚本创建插件目录,必定生成 .codex-plugin/plugin.json,内含完整 schema 结构、[TODO: ...] 占位值和完整的 interface 段。插件名按 skill-creator 的命名规则归一化为小写连字符形式(不超过 64 字符),目录名与清单中的 name 始终一致。可选参数还能一并生成 skills/、hooks/、scripts/、assets/、.mcp.json、.app.json 以及 marketplace.json 条目。

什么时候用它

  • 从零开始搭建一个本地 Codex 插件
  • 给已有插件补充 skills、hooks 或 MCP 配置目录
  • 在 .agents/plugins/marketplace.json 中登记插件及其 policy 和 category 字段
  • 在 ~/plugins 下创建 home-local 插件并配套独立的 marketplace 文件

技能文档

Plugin Creator

Quick Start

  1. Run the scaffold script:
  # Plugin names are normalized to lower-case hyphen-case and must be <= 64 chars.
  # The generated folder and plugin.json name are always the same.
# Run from repo root (or replace .agents/... with the absolute path to this SKILL).
# By default creates in /plugins/.
python3 .agents/skills/plugin-creator/scripts/create_basic_plugin.py 
  1. Open /.codex-plugin/plugin.json and replace [TODO: ...] placeholders.

  2. Generate or update the repo marketplace entry when the plugin should appear in Codex UI ordering:

# marketplace.json always lives at /.agents/plugins/marketplace.json
python3 .agents/skills/plugin-creator/scripts/create_basic_plugin.py my-plugin --with-marketplace

For a home-local plugin, treat `` as the root and use:

python3 .agents/skills/plugin-creator/scripts/create_basic_plugin.py my-plugin \
  --path ~/plugins \
  --marketplace-path ~/.agents/plugins/marketplace.json \
  --with-marketplace
  1. Generate/adjust optional companion folders as needed:
python3 .agents/skills/plugin-creator/scripts/create_basic_plugin.py my-plugin --path  \
  --with-skills --with-hooks --with-scripts --with-assets --with-mcp --with-apps --with-marketplace

is the directory where the plugin folder will be created (for example ~/code/plugins).

What this skill creates

  • If the user has not made the plugin location explicit, ask whether they want a repo-local plugin or a home-local plugin before generating marketplace entries.
  • Creates plugin root at ///.
  • Always creates ///.codex-plugin/plugin.json.
  • Fills the manifest with the full schema shape, placeholder values, and the complete interface section.
  • Creates or updates /.agents/plugins/marketplace.json when --with-marketplace is set.
    • If the marketplace file does not exist yet, seed top-level name plus interface.displayName placeholders before adding the first plugin entry.
  • `` is normalized using skill-creator naming rules:
    • My Plugin → my-plugin
    • My--Plugin → my-plugin
    • underscores, spaces, and punctuation are converted to -
    • result is lower-case hyphen-delimited with consecutive hyphens collapsed
  • Supports optional creation of:
    • skills/
    • hooks/
    • scripts/
    • assets/
    • .mcp.json
    • .app.json

Marketplace workflow

  • marketplace.json always lives at /.agents/plugins/marketplace.json.
  • For a home-local plugin, use the same convention with `` as the root: ~/.agents/plugins/marketplace.json plus ./plugins/.
  • Marketplace root metadata supports top-level name plus optional interface.displayName.
  • Treat plugin order in plugins[] as render order in Codex. Append new entries unless a user explicitly asks to reorder the list.
  • displayName belongs inside the marketplace interface object, not individual plugins[] entries.
  • Each generated marketplace entry must include all of:
    • policy.installation
    • policy.authentication
    • category
  • Default new entries to:
    • policy.installation: "AVAILABLE"
    • policy.authentication: "ON_INSTALL"
  • Override defaults only when the user explicitly specifies another allowed value.
  • Allowed policy.installation values:
    • NOT_AVAILABLE
    • AVAILABLE
    • INSTALLED_BY_DEFAULT
  • Allowed policy.authentication values:
    • ON_INSTALL
    • ON_USE
  • Treat policy.products as an override. Omit it unless the user explicitly requests product gating.
  • The generated plugin entry shape is:
{
  "name": "plugin-name",
  "source": {
    "source": "local",
    "path": "./plugins/plugin-name"
  },
  "policy": {
    "installation": "AVAILABLE",
    "authentication": "ON_INSTALL"
  },
  "category": "Productivity"
}
  • Use --force only when intentionally replacing an existing marketplace entry for the same plugin name.

  • If /.agents/plugins/marketplace.json does not exist yet, create it with top-level "name", an "interface" object containing "displayName", and a plugins array, then add the new entry.

  • For a brand-new marketplace file, the root object should look like:

{
  "name": "[TODO: marketplace-name]",
  "interface": {
    "displayName": "[TODO: Marketplace Display Name]"
  },
  "plugins": [
    {
      "name": "plugin-name",
      "source": {
        "source": "local",
        "path": "./plugins/plugin-name"
      },
      "policy": {
        "installation": "AVAILABLE",
        "authentication": "ON_INSTALL"
      },
      "category": "Productivity"
    }
  ]
}

Required behavior

  • Outer folder name and plugin.json "name" are always the same normalized plugin name.
  • Do not remove required structure; keep .codex-plugin/plugin.json present.
  • Keep manifest values as placeholders until a human or follow-up step explicitly fills them.
  • If creating files inside an existing plugin path, use --force only when overwrite is intentional.
  • Preserve any existing marketplace interface.displayName.
  • When generating marketplace entries, always write policy.installation, policy.authentication, and category even if their values are defaults.
  • Add policy.products only when the user explicitly asks for that override.
  • Keep marketplace source.path relative to repo root as ./plugins/.

Reference to exact spec sample

For the exact canonical sample JSON for both plugin manifests and marketplace entries, use:

  • references/plugin-json-spec.md

Validation

After editing SKILL.md, run:

python3 /scripts/quick_validate.py .agents/skills/plugin-creator

常见问题

生成的 plugin.json 里有什么?
包含完整 schema 结构、占位值和完整的 interface 段。所有值都保持 [TODO: ...] 占位状态,直到人工或后续步骤显式填写。
插件名是怎么处理的?
按 skill-creator 的命名规则归一化:下划线、空格和标点转为连字符,连续连字符合并,结果为小写且不超过 64 字符。外层目录名与 plugin.json 中的 name 始终相同。
marketplace 条目包含哪些字段?
每条都会写入 policy.installation(默认 AVAILABLE)、policy.authentication(默认 ON_INSTALL)和 category,source.path 保持相对仓库根目录的 ./plugins/。除非你明确要求做产品限制,否则不会写入 policy.products。

相关技能

从 AdMapix API 拉取广告创意、应用、榜单和收入预估等数据,原样返回结构化 JSON。

作者 fly0pants4.3k 次安装296 星标

把自然语言描述转为结构化 JSON,并由 mcp-diagram-generator MCP 服务生成 Draw.io、Mermaid 或 Excalidraw 图表文件。

作者 nssa.io1.0k 次安装47 星标

从 git 历史生成人-文件归属图,并给出巴士因子与敏感代码风险结论。

作者 OpenAI28.8k 星标

Deploy web projects to Netlify using the Netlify CLI (`npx netlify`). Use when the user asks to deploy, host, publish, or link a site/repo on Netlify, including preview and production deploys.

作者 OpenAI28.8k 星标

sentry

官方

Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry CLI; perform read-only queries using the `sentry` command

作者 OpenAI28.8k 星标

OpenAI 的更多技能

浏览全部技能

搭建和重构 ChatGPT Apps SDK 应用,把 MCP 服务器与 widget 界面组合起来。

作者 OpenAI28.8k 星标

基于文件里已发布的设计系统,把代码或描述转成完整的 Figma 页面。

作者 OpenAI28.8k 星标

按阶段把代码库转成对应的 Figma 设计系统,每个阶段都停下来等你确认。

作者 OpenAI28.8k 星标

figma-use

官方

在 Figma 文件里通过 Plugin API 执行 JavaScript,并避开那些容易踩的坑。

作者 OpenAI28.8k 星标

hatch-pet

官方

把概念、品牌线索或参考图做成通过校验的 8x9 Codex 宠物图集,附 QA 对照表和 pet.json 打包。

作者 OpenAI28.8k 星标

imagegen

官方

在 Codex 中生成或编辑位图,产出主视觉、精灵图、产品图或透明背景抠图。

作者 OpenAI28.8k 星标