Bootstrapping a Codex plugin directory (for when they're ready to use it)#459
Bootstrapping a Codex plugin directory (for when they're ready to use it)#459johno-stripe wants to merge 2 commits into
Conversation
…ly use the format in their own marketplace yet
![stripe-ai-sync[bot]](https://avatars.githubusercontent.com/u/856813?s=60&v=4){kind=small}
There was a problem hiding this comment.
This PR modifies files that are automatically synced from a centrally maintained copy at docs.stripe.com/.well-known/skills. Any changes made here will be overwritten by the next sync.
To make lasting changes, apply them to the source. You can find instructions at go/add-stripe-skill.
johno-stripe
requested review from
anthonydresser-stripe
and removed request for
matv-stripe
|
can we use the new logo? (http://go/logo) |
There was a problem hiding this comment.
This PR modifies files that are automatically synced from a centrally maintained copy at docs.stripe.com/.well-known/skills. Any changes made here will be overwritten by the next sync.
To make lasting changes, apply them to the source. You can find instructions at go/add-stripe-skill.
|
Plugged in the white-on-blurple parallelogram, @matv-stripe , matches up with our existing icon! Will merge if you're peaceful. |
matv-stripe
left a comment
matv-stripe
left a comment
There was a problem hiding this comment.
quick question but lgtm
| @@ -0,0 +1,33 @@ | |||
| { | |||
| "name": "stripe", | |||
| "version": "5.0.0", | |||
There was a problem hiding this comment.
do we need to run the same auto-plugin bumping stuff here?
There was a problem hiding this comment.
https://github.com/stripe/ai/pull/452/changes , i see it in version files so Im assuming that is working?
| "url": "https://stripe.com" | ||
| }, | ||
| "homepage": "https://stripe.com", | ||
| "repository": "https://github.com/openai/plugins", |
There was a problem hiding this comment.
should repository link to openai/plugins or to us?
2 participants
Summary
The OpenAI marketplace doesn't support adding third party Codex plugins yet, but they have defined a spec for how they should be packaged. I'm setting this up for now so that Stripes who want to make Codex-specific versions of Skills have a clear place to put them.
providers/codex/plugin/), mirroring the existing Claude and Cursor plugin structures..codex-plugin/plugin.json), app config (.app.json), marketplace entry, and app icon.stripe-best-practices,stripe-directory,stripe-projects,upgrade-stripe) into the new Codex plugin directory.scripts/sync.jsto include the Codex plugin in skill sync and version bumping.guard-skills.yml,sync-skills.yml) to cover the newproviders/codex/plugin/skills/**path.Test plan
node scripts/sync.jsand verify Codex skills stay in sync with Claude/Cursor skillsguard-skills.ymltriggers on changes toproviders/codex/plugin/skills/**sync-skills.ymlincludesproviders/codex/plugin/.codex-plugin/plugin.jsonin its git add step