chatgpt-plugin is for building, submitting or changing a ChatGPT plugin or Apps SDK app. ChatGPT and Codex share OpenAI’s plugin directory, and the skill works with any remote MCP server, in any language, behind any OAuth provider or none.
It lists the decisions to make before the first upload, the rules every submission meets, an eight-step stage order, and a checker script that validates the package folder and its ZIP before each upload.
What You Get
- A decision table covering sign-in, endpoint origin, tool list, publishing identity, data-residency project and availability
- Submission rules: authentication declared in mcp.json, discovery open to the portal scanner, _meta accepted on every request, no secrets in tools or replies, explicit tool annotations, listing copy without pricing
- An eight-step stage order from decision log to answering the review
- A list of six places where OpenAI’s pages disagree, with the stricter reading to follow
- check_package.py to validate a package folder and ZIP, with a test file that breaks a valid package one way at a time
Common Use Cases
- Preparing a first submission of an MCP server to OpenAI’s directory
- Checking a plugin ZIP before every upload
- Writing a privacy policy that names every field a reply returns
- Answering a review decision or changing a listed plugin
What Makes It Unique
It records what the portal and reviewers did in practice, dated, and says that OpenAI’s current pages win wherever they differ from the skill. It ties the ZIP to the product’s test suite so a hand-rebuilt ZIP cannot go stale, and it holds the privacy policy and reply fields equal both ways with a test. It works with any MCP server and does not need the mcp-server skill.
Under The Hood
The skill is markdown, four reference files, a receipts file and two Python scripts. The checker reads a local package folder and ZIP and exits with an error code when a rule fails; the test script builds a sample package and breaks it. The guidance tells the agent to read OpenAI’s developer pages (fetching them as markdown), connect a custom connector to the production server and call each tool, run routing evals against a local server, write package files and a ZIP, and record a review video. Portal steps such as the draft, domain verification and submission are done by the owner in OpenAI’s portal.