Skip to content

phuryn/product-engineering / app-stack/skills/chatgpt-plugin

chatgpt-plugin

Verified

Before building, submitting or changing a ChatGPT plugin or Apps SDK app: get it through OpenAI's directory review (auth, package, OAuth, data rules, portal).

FileKindSize
SKILL.mdskill md12.5 KB
receipts.mdmarkdown1.3 KB
references/package.mdmarkdown11.1 KB
references/portal-and-review.mdmarkdown13.2 KB
references/server-and-auth.mdmarkdown15.7 KB
references/tools-and-data.mdmarkdown12.4 KB
scripts/check_package.pyscript23.6 KB
scripts/test_check_package.pyscript9.5 KB

receipts.md

View on GitHub
# chatgpt-plugin: receipts

Each heading is a rule from `SKILL.md`, with the case that taught it.

## Verify the plugin against directory requirements before its first submission.

- `Undated`: Two products' submissions: a live Q&A product that submitted a plugin with no sign-in (rejected once, then resubmitted), and a monitoring product preparing one behind OAuth. They appear here only as examples.

- `Undated`: A mismatch with the legal pages was a rejection reason.

## Authentication is declared in `mcp.json`, per server, before the first upload.

- `2026-10`, an anonymous server whose first package declared nothing was taken for OAuth, signed in, and only a new plugin undid it.

## Every request's `params` may carry `_meta`, and the server accepts it.

- `2026-10-27`, twelve keys on one OAuth connector's call.

- `Undated`: A parser that refuses unknown keys there would refuse every one of those calls; one product's did, found in its code before any ChatGPT call.

## The privacy policy names every field a reply returns.

- `2026-10`, a policy that summarized was a rejection reason.

## Try a corrected ZIP first after a package rejection.

- `2026-10-19`, OpenAI support called a rejected plugin that could not be updated a known issue, with a new plugin as the fallback.
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall