feat(codex): add codex plugin and root marketplace - #3
minhthanhdang wants to merge 3 commits into
Conversation
xavierandueza
left a comment
xavierandueza
left a comment
There was a problem hiding this comment.
Just a nit on these - if we're doing things to publish these do we want skills in the individual folders vs having them at root?
WOuld be great to have a single source of truth, but not the end of the world if we can't
| "mcpServers": { | ||
| "readme": { | ||
| "type": "streamable-http", | ||
| "url": "https://docs.readme.com/mcp" |
There was a problem hiding this comment.
how come no bearer here? Is that just the way that the codex plugins work?
There was a problem hiding this comment.
yea.
re: skills at root
- Onboarding skills will be different for Claude and Codex.
- Can't submit to Claude if skills folder is outside the specified root
I'll leave it for now. To my engineering principles except when there is a published plugin standard agreed by all LLM providers, it's useless to think about a shared folder between them.
b5f979f to
33406b9
Compare
|
Moved to readmeio/agent-plugins#3. Same commits, same stack. The only content changes are the Closing here. @xavierandueza sorry, the approval does not travel with the move, so the new PR needs a fresh look. |
2 participants
Stacked on #2, merge that first.
🧰 Changes
Adds the Codex plugin under
codex/and a marketplace file at the repo root, socodex plugin marketplace add readmeio/readme-pluginsfollowed bycodex plugin add readme@readmeinstalls it. It uses the portable Agent Plugins layout (rootplugin.jsonandmcp.json) with thecom.openaiinterface block, which is the format OpenAI's current docs recommend and Codex 0.154.0 installs cleanly.The MCP server ships anonymous: Codex strips
Authorizationfrom plugin MCP configs, so the README tells users to register the server withcodex mcp addand--bearer-token-env-varfor write access. Skills are a copy ofclaude/skillsfor now.🧬 QA & Testing
installed, enabled, all three skills load asreadme:*.