Rank #4 of 5 in Agent Skills & Extensions
Access
Showcase


Products
OpenAI, product by product →OpenAI ships more than one product — each judged line competes in its own arena on the same stories as everyone else.
| Line | Arena | Rank | PA Score | Agent-ready |
|---|---|---|---|---|
| ChatGPT | AI Assistants | #1/9 | 38/100 | 49/100 |
| Codex | AI Coding Agents | #6/13 | 33/100 | 46/100 |
| Agents SDK | Agent Frameworks & SDKs | #2/9 | 37/100 | 55/100 |
| Pluginsthis page | Agent Skills & Extensions | #4/5 | 19/100 | 33/100 |
Not yet judged (6 — no arena where they compete): ChatGPT Work · Image generation (GPT-Image-2.5) · Codex Security · ChatKit · Agents API · API Platform
Try itExperimental
See what an agent can do with Codex Plugins before you ever sign up. Pick a story: recorded sessions replay real probe-harness transcripts; commands tagged live-capable can re-run against the real endpoint from our edge, right now (▶ run live — the exact same request, live and recorded lines always labeled); sandboxed self-drive sessions are designed and gated (docs/TRY-IT.md).
$curl -s https://raw.githubusercontent.com/openai/plugins/HEAD/.agents/plugins/marketplace.json | head -40recorded session — replayed, not liveVerified integrations
Connections to other tracked products — hover a chip for the verbatim evidence quote behind it.
By theme — the product's score on each story themeBy theme
Agent workflows — stories about agent workflows in this arenaAgent workflowsevidence →
Stories about agent workflows in this arena
Agenticness — how well agents can access and operate the productAgenticnessevidence →
How well agents can access and operate the product
Automation depth — how much of the product can run unattendedAutomation depthevidence →
How much of the product can run unattended
Cross agent portability — stories about cross agent portability in this arenaCross agent portabilityevidence →
Stories about cross agent portability in this arena
Discovery distribution — stories about discovery distribution in this arenaDiscovery distributionevidence →
Stories about discovery distribution in this arena
Docs onboarding — stories about docs onboarding in this arenaDocs onboardingevidence →
Stories about docs onboarding in this arena
Install experience — stories about install experience in this arenaInstall experienceevidence →
Stories about install experience in this arena
Openness — open source, data portability, and self-hosting storiesOpennessevidence →
Open source, data portability, and self-hosting stories
Privacy posture — data-handling and privacy storiesPrivacy postureevidence →
Data-handling and privacy stories
Safety review — stories about safety review in this arenaSafety reviewevidence →
Stories about safety review in this arena
Skill authoring — stories about skill authoring in this arenaSkill authoringevidence →
Stories about skill authoring in this arena
Testing quality — stories about testing quality in this arenaTesting qualityevidence →
Stories about testing quality in this arena
Versioning updates — stories about versioning updates in this arenaVersioning updatesevidence →
Stories about versioning updates in this arena
Story verdicts — every judged story with its evidenceStory verdicts
Follow the green: where the map greys out is where Codex Plugins stops today. ✓ full · ~ partial · ! disputed · — none · n/a not applicable.
Agent workflows — stories about agent workflows in this arenaAgent workflows
Stories about agent workflows in this arena
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
API surface
Drive the product through a documented public API
—0/10
Subscribe to events via webhooks
n/an/a
Build against official SDKs
~5/10
Issue scoped/least-privilege API credentials for an agent
—0/10
Connect an agent via an official MCP server
n/an/a
Download a machine-readable API spec (OpenAPI or equivalent)
—0/10
Rely on versioned APIs with a documented deprecation policy
—0/10
Test against a sandbox environment without touching production data
—–
Explore an interactive API reference with runnable examples
—0/10
CLI & headless
Use an official CLI
✓8/10
unlocks → Headless / CI
Run the product headlessly / in CI for automation
—0/10
Agentic features
Delegate tasks to a built-in AI assistant inside the product
✓7/10
Operate the product with natural-language commands
✓7/10
unlocks → Autonomous automations
Plug MCP servers into this product so it can use their tools
✓8/10
Get AI-generated insights and suggestions from my data inside the product
~6/10
Set up automations that run autonomously in the background
—0/10
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
Cross agent portability — stories about cross agent portability in this arenaCross agent portability
Stories about cross agent portability in this arena
Discovery distribution — stories about discovery distribution in this arenaDiscovery distribution
Stories about discovery distribution in this arena
Browse or search a catalog of available skills — a registry, leaderboard, or marketplace listing — before installing anything
✓8/10
Distribute a standard skill set to my whole team — via a marketplace, a shared repo, or files committed to the project
✓8/10
Installed skills trigger automatically from task context, with descriptions engineered so the agent activates the right skill at the right moment
~7/10
Docs onboarding — stories about docs onboarding in this arenaDocs onboarding
Stories about docs onboarding in this arena
Install experience — stories about install experience in this arenaInstall experience
Stories about install experience in this arena
Install
List what is installed and remove skills cleanly, without orphaned files or lingering instructions
~3/10
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
Safety review — stories about safety review in this arenaSafety review
Stories about safety review in this arena
Skill authoring — stories about skill authoring in this arenaSkill authoring
Stories about skill authoring in this arena
Testing quality — stories about testing quality in this arenaTesting quality
Stories about testing quality in this arena
Versioning updates — stories about versioning updates in this arenaVersioning updates
Stories about versioning updates in this arena
Sorted by importance (agentic first) (high → low) · 52/52 stories · click a row’s chevron for the rationale and evidence
Plug MCP servers into this product so it can use their tools G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | full | 8/10 | Cclaimed | |
Delegate tasks to a built-in AI assistant inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | full | 7/10 | Cclaimed | |
Connect an agent via an official MCP server G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | n/a | 0/10 | ||
Drive the product through a documented public API G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | none | 0/10 | ||
Use an official CLI G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 8/10 | Tprobed | |
Operate the product with natural-language commands G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 7/10 | Xcommunity | |
Get AI-generated insights and suggestions from my data inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 6/10 | Cclaimed | |
Build against official SDKs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 5/10 | Tprobed | |
Point an agent at llms.txt or agent-oriented docs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 5/10 | Tprobed | |
Download a machine-readable API spec (OpenAPI or equivalent) G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Explore an interactive API reference with runnable examples G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Issue scoped/least-privilege API credentials for an agent G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Rely on versioned APIs with a documented deprecation policy G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Run the product headlessly / in CI for automation G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Set up automations that run autonomously in the background G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Subscribe to events via webhooks G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | n/a | untested | none yet | |
Test against a sandbox environment without touching production data G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 1 | none | untested | none yet | |
Author a new skill from a documented template — a SKILL.md with name and description frontmatter — without reverse-engineering existing skills C Authoring | developer | Skill authoring — stories about skill authoring in this arenaSkill authoring | 3 | full | 8/10 | Xcommunity | |
Install a skill collection with one documented command — a package-manager one-liner, CLI, or in-agent marketplace command — and it is active in my next session C Install | developer | Install experience — stories about install experience in this arenaInstall experience | 3 | full | 7/10 | Cclaimed | |
Installed skills trigger automatically from task context, with descriptions engineered so the agent activates the right skill at the right moment C Triggering | developer | Discovery distribution — stories about discovery distribution in this arenaDiscovery distribution | 3 | partial | 7/10 | Xcommunity | |
A quickstart takes me from nothing to a working installed skill in under five minutes C Onboarding | developer | Docs onboarding — stories about docs onboarding in this arenaDocs onboarding | 3 | partial | 6/10 | Cclaimed | |
My coding agent can install a skill by itself — a non-interactive, promptless install path an agent can run headlessly end to end C Agent ops | ai-native user | Agent workflows — stories about agent workflows in this arenaAgent workflows | 3 | partial | 5/10 | Cclaimed | |
Review exactly what instructions and scripts a skill will add — list contents before installing and read every file afterward C Review | engineering-lead | Safety review — stories about safety review in this arenaSafety review | 3 | partial | 5/10 | Cclaimed | |
Define rules that trigger actions automatically on events G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 3 | partial | 3/10 | Cclaimed | |
Install the same collection into multiple different coding agents — Claude Code, Codex, Cursor, and others — with per-harness instructions C Portability | developer | Cross agent portability — stories about cross agent portability in this arenaCross agent portability | 3 | none | 0/10 | ||
There is a documented update path — marketplace auto-updates or an explicit update command — so I get fixes without reinstalling from scratch C Updates | developer | Versioning updates — stories about versioning updates in this arenaVersioning updates | 3 | none | 0/10 | ||
Export all of my data in open formats and leave G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | none | untested | none yet | |
Prevent my data from being used to train AI models G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 3 | none | untested | none yet | |
Self-host the core product G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | none | untested | none yet | |
Browse or search a catalog of available skills — a registry, leaderboard, or marketplace listing — before installing anything C Discovery | developer | Discovery distribution — stories about discovery distribution in this arenaDiscovery distribution | 2 | full | 8/10 | Cclaimed | |
Distribute a standard skill set to my whole team — via a marketplace, a shared repo, or files committed to the project C Distribution | engineering-lead | Discovery distribution — stories about discovery distribution in this arenaDiscovery distribution | 2 | full | 8/10 | Xcommunity | |
My agent can author and package a new skill end to end by following the project's own spec, template, or meta-skill C Agent ops | ai-native user | Agent workflows — stories about agent workflows in this arenaAgent workflows | 2 | full | 8/10 | Xcommunity | |
The collection ships a meta-skill or tool that guides my agent through writing, improving, and packaging new skills C Authoring | developer | Skill authoring — stories about skill authoring in this arenaSkill authoring | 2 | full | 8/10 | Xcommunity | |
Every skill documents what it does and when it activates, so I can predict my agent's new behavior before it surprises me C Onboarding | developer | Docs onboarding — stories about docs onboarding in this arenaDocs onboarding | 2 | partial | 7/10 | Xcommunity | |
Install only the specific skills I want from a collection instead of taking the whole bundle C Install | developer | Install experience — stories about install experience in this arenaInstall experience | 2 | partial | 6/10 | Cclaimed | |
Skills are plain markdown files and folders I can read, copy, and carry to another harness — not a proprietary binary format C Portability | developer | Cross agent portability — stories about cross agent portability in this arenaCross agent portability | 2 | partial | 6/10 | Cclaimed | |
Skills follow the open Agent Skills specification so the same skill folder is valid beyond this one vendor's tooling C Spec | developer | Skill authoring — stories about skill authoring in this arenaSkill authoring | 2 | partial | 6/10 | Xcommunity | |
Choose install scope — project-local files committed with my repo, or user-global across all projects C Install | developer | Install experience — stories about install experience in this arenaInstall experience | 2 | partial | 5/10 | Cclaimed | |
The project documents its security posture — what skills can execute, the trust model for third-party skills, and any telemetry or data collection C Trust | engineering-lead | Safety review — stories about safety review in this arenaSafety review | 2 | partial | 4/10 | Cclaimed | |
Read the product's source under an open license G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | partial | 3/10 | Cclaimed | |
Control data retention and deletion G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | 0/10 | ||
Do everything through the API that I can do in the UI G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | none | 0/10 | ||
The collection maintains tests or evals for its skills so changes are verified against regressions rather than shipped on vibes C Testing | developer | Testing quality — stories about testing quality in this arenaTesting quality | 2 | none | 0/10 | ||
Choose where my data is stored (region/residency) G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | n/a | untested | none yet | |
Opt out of telemetry and usage tracking G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | untested | none yet | |
Perform bulk operations across many items at once G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | none | untested | none yet | |
Schedule recurring jobs or workflows G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | none | untested | none yet | |
The collection is actively maintained — recent releases, triaged issues, and accepted community contributions C Maintenance | developer | Testing quality — stories about testing quality in this arenaTesting quality | 2 | none | untested | none yet | |
List what is installed and remove skills cleanly, without orphaned files or lingering instructions C Lifecycle | developer | Install experience — stories about install experience in this arenaInstall experience | 1 | partial | 3/10 | Cclaimed | |
Control when skill changes reach my team — pinned versions or a lockfile rather than silent behind-the-back updates C Pinning | engineering-lead | Versioning updates — stories about versioning updates in this arenaVersioning updates | 1 | none | 0/10 | ||
Version, review, and roll back my automations G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 1 | none | 0/10 | ||
Releases ship with notes or a changelog so I can see what changed in the skills before I take an update C Updates | developer | Versioning updates — stories about versioning updates in this arenaVersioning updates | 1 | none | untested | none yet |
Opportunities — the stories that would move this product's scores, from its own judged verdictsOpportunitiestop 8 of 39 stories with headroom
What would move Codex Plugins’s scores — derived from its own judged verdicts, biggest headroom first. Each line quotes what the judge found missing; shipping it (or evidencing it publicly) is the fix.
Agenticness — how well agents can access and operate the productDrive the product through a documented public API
nonemoves agent-readyimpact 45
Evidence shows Codex Plugins uses MCP to let plugins expose capabilities *to* Codex/ChatGPT, and offers CLI commands (`codex plugin marketplace add`, `/plugins`) for local plugin management, but there is no documented public REST/GraphQL API for programmatically driving the Codex Plugins product itself — the direct OpenAPI probe returned 404 on all candidate spec paths, confirming no discoverable public API surface.
Versioning updates — stories about versioning updates in this arenaThere is a documented update path — marketplace auto-updates or an explicit update command — so I get fixes without reinstalling from scratch
nonemoves PA Scoreimpact 30
Evidence covers plugin installation (`/plugins`, `codex plugin marketplace add`) and creation/submission workflows, but nowhere documents an explicit update/upgrade command or auto-update behavior for already-installed plugins to receive fixes without reinstalling.
Cross agent portability — stories about cross agent portability in this arenaInstall the same collection into multiple different coding agents — Claude Code, Codex, Cursor, and others — with per-harness instructions
nonemoves PA Scoreimpact 30
All evidence describes installing plugins/skills within OpenAI's own ecosystem (Codex CLI, ChatGPT desktop/Chat/Work) — there is no evidence of a single collection being installed into Claude Code, Cursor, or other third-party coding agents.
Openness — open source, data portability, and self-hosting storiesExport all of my data in open formats and leave
nonemoves PA Scoreimpact 30
No evidence of any data export feature, open-format export, or account/data portability mechanism for Codex Plugins; the documentation focuses on plugin/skill installation and creation, not user data export or exit.
Openness — open source, data portability, and self-hosting storiesSelf-host the core product
nonemoves PA Scoreimpact 30
The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na".
Privacy posture — data-handling and privacy storiesPrevent my data from being used to train AI models
nonemoves PA Scoreimpact 30
The evidence pack covers plugin/skill installation, marketplace, and OAuth sign-in scope, but contains no mention of data-training opt-out or AI-training data controls for Codex Plugins.
Agenticness — how well agents can access and operate the productSet up automations that run autonomously in the background
nonemoves Built-in AIimpact 30
Missing: any scheduler/cron/trigger mechanism, background/always-on execution mode, or evidence of unattended autonomous runs.
Agenticness — how well agents can access and operate the productRun the product headlessly / in CI for automation
nonemoves agent-readyimpact 30
Missing: any mention of a non-interactive/headless invocation mode, CI examples, or automation-friendly APIs for plugins/skills.
Showing the top 8 of 39 — every none/partial verdict in the story verdicts table is headroom.
Think a verdict is wrong? Every verdicts-table row has a Flag link — see the methodology.
Coverage map — which docs area, API section, or community source covers which judged storiesCoverage map7 surfaces · 26 covered stories
Where the cited evidence behind each covered verdict came from — the same citations the verdicts table shows, no extra judging.
docs24 stories
- My agent can author and package a new skill end to end by following the project's own spec, template, or meta-skill
- My coding agent can install a skill by itself — a non-interactive, promptless install path an agent can run headlessly end to end
- Point an agent at llms.txt or agent-oriented docs
- Plug MCP servers into this product so it can use their tools
- Use an official CLI
- Get AI-generated insights and suggestions from my data inside the product
- Delegate tasks to a built-in AI assistant inside the product
- Operate the product with natural-language commands
- Define rules that trigger actions automatically on events
- Skills are plain markdown files and folders I can read, copy, and carry to another harness — not a proprietary binary format
- Browse or search a catalog of available skills — a registry, leaderboard, or marketplace listing — before installing anything
- Distribute a standard skill set to my whole team — via a marketplace, a shared repo, or files committed to the project
- Installed skills trigger automatically from task context, with descriptions engineered so the agent activates the right skill at the right moment
- A quickstart takes me from nothing to a working installed skill in under five minutes
- Every skill documents what it does and when it activates, so I can predict my agent's new behavior before it surprises me
- Install a skill collection with one documented command — a package-manager one-liner, CLI, or in-agent marketplace command — and it is active in my next session
- Choose install scope — project-local files committed with my repo, or user-global across all projects
- Install only the specific skills I want from a collection instead of taking the whole bundle
- List what is installed and remove skills cleanly, without orphaned files or lingering instructions
- Review exactly what instructions and scripts a skill will add — list contents before installing and read every file afterward
- The project documents its security posture — what skills can execute, the trust model for third-party skills, and any telemetry or data collection
- Author a new skill from a documented template — a SKILL.md with name and description frontmatter — without reverse-engineering existing skills
- The collection ships a meta-skill or tool that guides my agent through writing, improving, and packaging new skills
- Skills follow the open Agent Skills specification so the same skill folder is valid beyond this one vendor's tooling
Plugins docs16 stories
- My agent can author and package a new skill end to end by following the project's own spec, template, or meta-skill
- My coding agent can install a skill by itself — a non-interactive, promptless install path an agent can run headlessly end to end
- Plug MCP servers into this product so it can use their tools
- Use an official CLI
- Build against official SDKs
- Get AI-generated insights and suggestions from my data inside the product
- Skills are plain markdown files and folders I can read, copy, and carry to another harness — not a proprietary binary format
- Browse or search a catalog of available skills — a registry, leaderboard, or marketplace listing — before installing anything
- Distribute a standard skill set to my whole team — via a marketplace, a shared repo, or files committed to the project
- A quickstart takes me from nothing to a working installed skill in under five minutes
- Install a skill collection with one documented command — a package-manager one-liner, CLI, or in-agent marketplace command — and it is active in my next session
- List what is installed and remove skills cleanly, without orphaned files or lingering instructions
- Review exactly what instructions and scripts a skill will add — list contents before installing and read every file afterward
- The project documents its security posture — what skills can execute, the trust model for third-party skills, and any telemetry or data collection
- Author a new skill from a documented template — a SKILL.md with name and description frontmatter — without reverse-engineering existing skills
- The collection ships a meta-skill or tool that guides my agent through writing, improving, and packaging new skills
Hacker News8 stories
- My agent can author and package a new skill end to end by following the project's own spec, template, or meta-skill
- Operate the product with natural-language commands
- Distribute a standard skill set to my whole team — via a marketplace, a shared repo, or files committed to the project
- Installed skills trigger automatically from task context, with descriptions engineered so the agent activates the right skill at the right moment
- Every skill documents what it does and when it activates, so I can predict my agent's new behavior before it surprises me
- Author a new skill from a documented template — a SKILL.md with name and description frontmatter — without reverse-engineering existing skills
- The collection ships a meta-skill or tool that guides my agent through writing, improving, and packaging new skills
- Skills follow the open Agent Skills specification so the same skill folder is valid beyond this one vendor's tooling
GitHub README7 stories
- My coding agent can install a skill by itself — a non-interactive, promptless install path an agent can run headlessly end to end
- Get AI-generated insights and suggestions from my data inside the product
- Browse or search a catalog of available skills — a registry, leaderboard, or marketplace listing — before installing anything
- Distribute a standard skill set to my whole team — via a marketplace, a shared repo, or files committed to the project
- Install only the specific skills I want from a collection instead of taking the whole bundle
- Read the product's source under an open license
- Review exactly what instructions and scripts a skill will add — list contents before installing and read every file afterward
Probe proofs — replayable recordings from the probe harnessProbe proofs
Replayable recordings from our probe harness — see the Prove-It protocol to submit one.
$curl -s https://raw.githubusercontent.com/openai/plugins/HEAD/.agents/plugins/marketplace.json | head -40reproduced$ curl -s https://raw.githubusercontent.com/openai/plugins/HEAD/.agents/plugins/marketplace.json | head -40
{
"name": "openai-curated",
"interface": {
"displayName": "Codex official"
},
"plugins": [
{
"name": "linear",
"source": {
"source": "local",
"path": "./plugins/linear"
},
"policy": {
"installation": "AVAILABLE",
"authentication": "ON_INSTALL"
},
"category": "Productivity"
},
{
"name": "atlassian-rovo",
"source": {
"source": "local",
"path": "./plugins/atlassian-rovo"
},
"policy": {
"installation": "AVAILABLE",
"authentication": "ON_INSTALL"
},
"category": "Productivity"
},
{
"name": "google-calendar",
"source": {
"source": "local",
"path": "./plugins/google-calendar"
},
"policy": {
"installation": "AVAILABLE",
"authentication": "ON_INSTALL"
},
$npx -y skills add openai/plugins --skill plugin-creator -a codex -y --copy # in a scratch dir, then print installed SKILL.md frontmatterreproduced$ npx -y skills add openai/plugins --skill plugin-creator -a codex -y --copy # in a scratch dir, then print installed SKILL.md frontmatter \ ███████╗██╗ ██╗██╗██╗ ██╗ ███████╗ ██╔════╝██║ ██╔╝██║██║ ██║ ██╔════╝ ███████╗█████╔╝ ██║██║ ██║ ███████╗ ╚════██║██╔═██╗ ██║██║ ██║ ╚════██║ ███████║██║ ██╗██║███████╗███████╗███████║ ╚══════╝╚═╝ ╚═╝╚═╝╚══════╝╚══════╝╚══════╝ ┌ skills │ ◇ Source: https://github.com/openai/plugins.git │ [ 3 5 m ◒ [ 3 9m C l o n i n g r e p o s i t o r y … [ 3 5 m ◐ [ 3 9m C l o n i n g r e p o s i t o r y … [ 3 5 m ◓ [ 3 9m C l o n i n g r e p o s i t o r y … [ 3 5 m ◑ [ 3 9m C l o n i n g r e p o s i t o r y … [ 3 5 m ◒ [ 3 9m C l o n i n g r e p o s i t o r y … [ 3 5 m ◐ [ 3 9m C l o n i n g r e p o s i t o r y … [ 3 5 m ◓ [ 3 9m C l o n i n g r e p o s i t o r y … [ 3 5 m ◑ [ 3 9m C l o n i n g r e p o s i t o r y … [ 3 5 m ◒ [ 3 9m C l o n i n g r e p o s i t o r y … . [ 3 5 m ◐ [ 3 9m C l o n i n g r e p o s i t o r y … . [ 3 5 m ◓ [ 3 9m C l o n i n g r e p o s i t o r y … . [ 3 5 m ◑ [ 3 9m C l o n i n g r e p o s i t o r y … . [ 3 5 m ◒ [ 3 9m C l o n i n g r e p o s i t o r y … . [ 3 5 m ◐ [ 3 9m C l o n i n g r e p o s i t o r y … . [ 3 5 m ◓ [ 3 9m C l o n i n g r e p o s i t o r y … . [ 3 5 m ◑ [ 3 9m C l o n i n g r e p o s i t o r y … . [ 3 5 m ◒ [ 3 9m C l o n i n g r e p o s i t o r y … . . [ 3 5 m ◐ [ 3 9m C l o n i n g r e p o s i t o r y … . . [ 3 5 m ◓ [ 3 9m C l o n i n g r e p o s i t o r y … . . [ 3 5 m ◑ [ 3 9m C l o n i n g r e p o s i t o r y … . . [ 3 5 m ◒ [ 3 9m C l o n i n g r e p o s i t o r y … . . [ 3 5 m ◐ [ 3 9m C l o n i n g r e p o s i t o r y … . . [ 3 5 m ◓ [ 3 9m C l o n i n g r e p o s i t o r y … . . [ 3 5 m ◑ [ 3 9m C l o n i n g r e p o s i t o r y … . . [ 3 5 m ◒ [ 3 9m C l o n i n g r e p o s i t o r y … . . . [ 3 5 m ◐ [ 3 9m C l o n i n g r e p o s i t o r y … . . . [ 3 5 m ◓ [ 3 9m C l o n i n g r e p o s i t o r y … . . . [ 3 5 m ◑ [ 3 9m C l o n i n g r e p o s i t o r y … . . . [ 3 5 m ◒ [ 3 9m C l o n i n g r e p o s i t o r y … . . . [ 3 5 m ◐ [ 3 9m C l o n i n g r e p o s i t o r y … . . . [ 3 5 m ◓ [ 3 9m C l o n i n g r e p o s i t o r y … . . . [ 3 5 m ◑ [ 3 9m C l o n i n g r e p o s i t o r y … . . . [ 3 5 m ◒ [ 3 9m C l o n i n g r e p o s i t o r y … . . . [ 3 5 m ◐ [ 3 9m C l o n i n g r e p o s i t o r y … [ 3 5 m ◓ [ 3 9m C l o n i n g r e p o s i t o r y … [ 3 5 m ◑ [ 3 9m C l o n i n g r e p o s i t o r y … [ 3 5 m ◒ [ 3 9m C l o n i n g r e p o s i t o r y … [ 3 5 m ◐ [ 3 9m C l o n i n g r e p o s i t o r y … [ 3 5 m ◓ [ 3 9m C l o n i n g r e p o s i t o r y … [ 3 5 m ◑ [ 3 9m C l o n i n g r e p o s i t o r y … [ 3 5 m ◒ [ 3 9m C l o n i n g r e p o s i t o r y … [ 3 5 m ◐ [ 3 9m C l o n i n g r e p o s i t o r y … . [ 3 5 m ◓ [ 3 9m C l o n i n g r e p o s i t o r y … . [ 3 5 m ◑ [ 3 9m C l o n i n g r e p o s i t o r y … . [ 3 5 m ◒ [ 3 9m C l o n i n g r e p o s i t o r y … . [ 3 5 m ◐ [ 3 9m C l o n i n g r e p o s i t o r y … . [ 3 5 m ◓ [ 3 9m C l o n i n g r e p o s i t o r y … . [ 3 5 m ◑ [ 3 9m C l o n i n g r e p o s i t o r y … . [ 3 5 m ◒ [ 3 9m C l o n i n g r e p o s i t o r y … . [ 3 5 m ◐ [ 3 9m C l o n i n g r e p o s i t o r y … . . [ 3 5 m ◓ [ 3 9m C l o n i n g r e p o s i t o r y … . . [ 3 5 m ◑ [ 3 9m C l o n i n g r e p o s i t o r y … . . [ 3 5 m ◒ [ 3 9m C l o n i n g r e p o s i t o r y … . . [ 3 5 m ◐ [ 3 9m C l o n i n g r e p o s i t o r y … . . [ 3 5 m ◓ [ 3 9m C l o n i n g r e p o s i t o r y … . . [ 3 5 m ◑ [ 3 9m C l o n i n g r e p o s i t o r y … . . [ 3 5 m ◒ [ 3 9m C l o n i n g r e p o s i t o r y … . . [ 3 5 m ◐ [ 3 9m C l o n i n g r e p o s i t o r y … . . . [ 3 5 m ◓ [ 3 9m C l o n i n g r e p o s i t o r y … . . . [ 3 5 m ◑ [ 3 9m C l o n i n g r e p o s i t o r y … . . . [ 3 5 m ◒ [ 3 9m C l o n i n g r e p o s i t o r y … . . . [ 3 5 m ◐ [ 3 9m C l o n i n g r e p o s i t o r y … . . . [ 3 5 m ◓ [ 3 9m C l o n i n g r e p o s i t o r y … . . . [ 3 5 m ◑ [ 3 9m C l o n i n g r e p o s i t o r y … . . . [ 3 5 m ◒ [ 3 9m C l o n i n g r e p o s i t o r y … . . . [ 3 5 m ◐ [ 3 9m C l o n i n g r e p o s i t o r y … . . . [ 3 5 m ◓ [ 3 9m C l o n i n g r e p o s i t o r y … [ 3 5 m ◑ [ 3 9m C l o n i n g r e p o s i t o r y … [ 3 5 m ◒ [ 3 9m C l o n i n g r e p o s i t o r y … [ 3 5 m ◐ [ 3 9m C l o n i n g r e p o s i t o r y … [ 3 5 m ◓ [ 3 9m C l o n i n g r e p o s i t o r y … [ 3 5 m ◑ [ 3 9m C l o n i n g r e p o s i t o r y … [ 3 5 m ◒ [ 3 9m C l o n i n g r e p o s i t o r y … [ 3 5 m ◐ [ 3 9m C l o n i n g r e p o s i t o r y … [ 3 5 m ◓ [ 3 9m C l o n i n g r e p o s i t o r y … . [ 3 5 m ◑ [ 3 9m C l o n i n g r e p o s i t o r y … . [ 3 5 m ◒ [ 3 9m C l o n i n g r e p o s i t o r y … . [ 3 5 m ◐ [ 3 9m C l o n i n g r e p o s i t o r y … . [ 3 5 m ◓ [ 3 9m C l o n i n g r e p o s i t o r y … . [ 3 5 m ◑ [ 3 9m C l o n i n g r e p o s i t o r y … . [ 3 5 m ◒ [ 3 9m C l o n i n g r e p o s i t o r y … . [ 3 5 m ◐ [ 3 9m C l o n i n g r e p o s i t o r y … . [ 3 5 m ◓ [ 3 9m C l o n i n g r e p o s i t o r y … . . [ 3 5 m ◑ [ 3 9m C l o n i n g r e p o s i t o r y … . . [ 3 5 m ◒ [ 3 9m C l o n i n g r e p o s i t o r y … . . [ 3 5 m ◐ [ 3 9m C l o n i n g r e p o s i t o r y … . . [ 3 5 m ◓ [ 3 9m C l o n i n g r e p o s i t o r y … . . [ 3 5 m ◑ [ 3 9m C l o n i n g r e p o s i t o r y … . . [ 3 5 m ◒ [ 3 9m C l o n i n g r e p o s i t o r y … . . [ 3 5 m ◐ [ 3 9m C l o n i n g r e p o s i t o r y … . . [ 3 5 m ◓ [ 3 9m C l o n i n g r e p o s i t o r y … . . . [ 3 5 m ◑ [ 3 9m C l o n i n g r e p o s i t o r y … . . . [ 3 5 m ◒ [ 3 9m C l o n i n g r e p o s i t o r y … . . . [ 3 5 m ◐ [ 3 9m C l o n i n g r e p o s i t o r y … . . . [ 3 5 m ◓ [ 3 9m C l o n i n g r e p o s i t o r y … . . . [ 3 5 m ◑ [ 3 9m C l o n i n g r e p o s i t o r y … . . . [ 3 5 m ◒ [ 3 9m C l o n i n g r e p o s i t o r y … . . . [ 3 5 m ◐ [ 3 9m C l o n i n g r e p o s i t o r y … . . . [ 3 5 m ◓ [ 3 9m C l o n i n g r e p o s i t o r y … . . . [ 3 5 m ◑ [ 3 9m C l o n i n g r e p o s i t o r y … [ 3 5 m ◒ [ 3 9m C l o n i n g r e p o s i t o r y … [ 3 5 m ◐ [ 3 9m C l o n i n g r e p o s i t o r y … [ 3 5 m ◓ [ 3 9m C l o n i n g r e p o s i t o r y … [ 3 5 m ◑ [ 3 9m C l o n i n g r e p o s i t o r y … [ 3 5 m ◒ [ 3 9m C l o n i n g r e p o s i t o r y … [ 3 5 m ◐ [ 3 9m C l o n i n g r e p o s i t o r y … [ 3 5 m ◓ [ 3 9m C l o n i n g r e p o s i t o r y … [ 3 5 m ◑ [ 3 9m C l o n i n g r e p o s i t o r y … . [ 3 5 m ◒ [ 3 9m C l o n i n g r e p o s i t o r y … . [ 3 5 m ◐ [ 3 9m C l o n i n g r e p o s i t o r y … . [ 3 5 m ◓ [ 3 9m C l o n i n g r e p o s i t o r y … . [ 3 5 m ◑ [ 3 9m C l o n i n g r e p o s i t o r y … .◇ Repository cloned │ ◇ Found 1 skill │ ● Selected 1 skill: plugin-creator │ ◇ Installation Summary ─╮ │ │ │ │ │ │ │ [ │ │ 3 │ │ 6 │ │ m │ │ . │ │ / │ │ . │ │ a │ │ g │ │ e │ │ n │ │ t │ │ s │ │ / │ │ s │ │ k │ │ i │ │ l │ │ l │ │ s │ │ / │ │ p │ │ l │ │ u │ │ g │ │ i │ │ n │ │ - │ │ c │ │ r │ │ e │ │ a │ │ t │ │ o │ │ r │ │ │ │ [ │ │ 3 │ │ 9m │ │ │ │ │ │ │ │ │ │ [ │ │ 2 │ │ m │ │ c │ │ o │ │ p │ │ y │ │ │ │ → │ │ │ │ [ │ │ 2 │ │ 2m │ │ │ │ C │ │ o │ │ d │ │ e │ │ x │ │ │ ├────────────────────────╯ │ ◇ Security Risk Assessments ─╮ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ [ │ │ 2 │ │ m │ │ G │ │ e │ │ n │ │ │ │ [ │ │ 2 │ │ 2m │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ [ │ │ 2 │ │ m │ │ S │ │ o │ │ c │ │ k │ │ e │ │ t │ │ │ │ [ │ │ 2 │ │ 2m │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ [ │ │ 2 │ │ m │ │ S │ │ n │ │ y │ │ k │ │ │ │ [ │ │ 2 │ │ 2m │ │ │ │ │ │ [ │ │ 3 │ │ 6 │ │ m │ │ p │ │ l │ │ u │ │ g │ │ i │ │ n │ │ - │ │ c │ │ r │ │ e │ │ a │ │ t │ │ o │ │ r │ │ │ │ [ │ │ 3 │ │ 9m │ │ │ │ │ │ │ │ [ │ │ 3 │ │ 2 │ │ m │ │ S │ │ a │ │ f │ │ e │ │ │ │ [ │ │ 3 │ │ 9m │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ [ │ │ 3 │ │ 2 │ │ m │ │ 0 │ │ │ │ a │ │ l │ │ e │ │ r │ │ t │ │ s │ │ │ │ [ │ │ 3 │ │ 9m │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ [ │ │ 3 │ │ 2 │ │ m │ │ L │ │ o │ │ w │ │ │ │ R │ │ i │ │ s │ │ k │ │ │ │ [ │ │ 3 │ │ 9m │ │ │ │ │ │ │ │ [ │ │ 2 │ │ m │ │ D │ │ e │ │ t │ │ a │ │ i │ │ l │ │ s │ │ : │ │ │ │ [ │ │ 2 │ │ 2m │ │ │ │ │ │ [ │ │ 2 │ │ m │ │ h │ │ t │ │ t │ │ p │ │ s │ │ : │ │ / │ │ / │ │ s │ │ k │ │ i │ │ l │ │ l │ │ s │ │ . │ │ s │ │ h │ │ / │ │ o │ │ p │ │ e │ │ n │ │ a │ │ i │ │ / │ │ p │ │ l │ │ u │ │ g │ │ i │ │ n │ │ s │ │ │ │ [ │ │ 2 │ │ 2m │ │ │ ├─────────────────────────────╯ │ ◇ Installation complete │ ◇ Installed 1 skill ─╮ │ │ │ │ │ │ │ [ │ │ 3 │ │ 2 │ │ m │ │ ✓ │ │ │ │ [ │ │ 3 │ │ 9m │ │ │ │ p │ │ l │ │ u │ │ g │ │ i │ │ n │ │ - │ │ c │ │ r │ │ e │ │ a │ │ t │ │ o │ │ r │ │ │ │ │ │ [ │ │ 2 │ │ m │ │ ( │ │ c │ │ o │ │ p │ │ i │ │ e │ │ d │ │ ) │ │ │ │ [ │ │ 2 │ │ 2m │ │ │ │ │ │ │ │ │ │ [ │ │ 2 │ │ m │ │ → │ │ │ │ [ │ │ 2 │ │ 2m │ │ │ │ . │ │ / │ │ . │ │ a │ │ g │ │ e │ │ n │ │ t │ │ s │ │ / │ │ s │ │ k │ │ i │ │ l │ │ l │ │ s │ │ / │ │ p │ │ l │ │ u │ │ g │ │ i │ │ n │ │ - │ │ c │ │ r │ │ e │ │ a │ │ t │ │ o │ │ r │ │ │ ├─────────────────────╯ │ └ Done! Review skills before use; they run with full agent permissions. \--- installed SKILL.md frontmatter --- --- name: plugin-creator description: Create and scaffold plugin directories for Codex with a required `.codex-plugin/plugin.json`, optional plugin folders/files, and baseline placeholders you can edit before publishing or testing. Use when Codex needs to create a new personal plugin, add optional plugin structure, or generate or update personal or repo-root `.agents/plugins/marketplace.json` entries for plugin ordering and availability metadata.
Claims vs evidence — vendor claims reconciled against independent verdictsClaims vs evidence
4 of 11 testable claims verified · 0 contradicted → integrity 36/100
24 distinct capability claims found in Codex Plugins’s own claimed-docs/GitHub materials, reconciled against our judge’s independent verdicts.
4
Verified
7
Unverified
0
Contradicted
15
Undersold
Verified (5)
“A skill-creation assistant interactively asks what the skill does, when it triggers, and whether it needs scripts”
The collection ships a meta-skill or tool that guides my agent through writing, improving, and packaging new skillsfullproof ↗
“Teams can check in skills scoped to a specific working folder like a microservice or module”
Distribute a standard skill set to my whole team — via a marketplace, a shared repo, or files committed to the projectfullproof ↗
“Built-in '@plugin-creator' skill scaffolds the plugin.json manifest and can generate a local marketplace entry for testing”
The collection ships a meta-skill or tool that guides my agent through writing, improving, and packaging new skillsfullproof ↗
“A skill is defined as a directory with a SKILL.md file (with required name and description) plus optional scripts/references”
Author a new skill from a documented template — a SKILL.md with name and description frontmatter — without reverse-engineering existing skillsfullproof ↗
“A recorder can capture a workflow demonstration and draft a reusable skill from it”
My agent can author and package a new skill end to end by following the project's own spec, template, or meta-skillfullproof ↗
Unverified (7)
“'/plugins' command opens an in-CLI plugin browser to explore available plugins”
Browse or search a catalog of available skills — a registry, leaderboard, or marketplace listing — before installing anythingfullproof ↗
“'$skill-installer' lets you add curated skills beyond the built-ins for your local Codex setup”
My coding agent can install a skill by itself — a non-interactive, promptless install path an agent can run headlessly end to endpartialproof ↗
“'codex plugin marketplace add' command adds and tracks a marketplace source instead of manual config editing”
Install a skill collection with one documented command — a package-manager one-liner, CLI, or in-agent marketplace command — and it is active in my next sessionfullproof ↗
“Plugin-creator skill wires up an MCP server as part of creating a new plugin”
Plug MCP servers into this product so it can use their toolsfullproof ↗
“Codex scans .agents/skills in every directory from cwd up to the repo root, enabling project-scoped skill discovery”
Choose install scope — project-local files committed with my repo, or user-global across all projectspartialproof ↗
“Signing in with ChatGPT only shares name, email, and profile picture, and does not grant plugin data access or auto-approve actions”
The project documents its security posture — what skills can execute, the trust model for third-party skills, and any telemetry or data collectionpartialproof ↗
“skill-installer can target and install a single named skill (e.g. linear) rather than a whole bundle”
Install only the specific skills I want from a collection instead of taking the whole bundlepartialproof ↗
Undersold (15)
Point an agent at llms.txt or agent-oriented docspartialproof ↗
Get AI-generated insights and suggestions from my data inside the productpartialproof ↗
Delegate tasks to a built-in AI assistant inside the productfullproof ↗
Operate the product with natural-language commandsfullproof ↗
Define rules that trigger actions automatically on eventspartialproof ↗
Skills are plain markdown files and folders I can read, copy, and carry to another harness — not a proprietary binary formatpartialproof ↗
Installed skills trigger automatically from task context, with descriptions engineered so the agent activates the right skill at the right momentpartialproof ↗
A quickstart takes me from nothing to a working installed skill in under five minutespartialproof ↗
Every skill documents what it does and when it activates, so I can predict my agent's new behavior before it surprises mepartialproof ↗
List what is installed and remove skills cleanly, without orphaned files or lingering instructionspartialproof ↗
Read the product's source under an open licensepartialproof ↗
Review exactly what instructions and scripts a skill will add — list contents before installing and read every file afterwardpartialproof ↗
Skills follow the open Agent Skills specification so the same skill folder is valid beyond this one vendor's toolingpartialproof ↗
Claims outside our story set (12)
Real capability claims found in Codex Plugins’s own materials, but no story in this arena’s taxonomy covers them yet — that’s feedback on the taxonomy, not a mark against the product.
“Security plugin can scan authorized code and confirm plausible vulnerability findings”
source ↗“Gmail plugin lets Codex work with Gmail”
source ↗“Google Drive plugin works across Drive, Docs, Sheets, and Slides”
source ↗“Slack plugin can summarize channels or draft replies”
source ↗“A plugin can read/search iMessage, SMS, RCS chats and send messages on the user's behalf”
source ↗“Figma plugin provides use_figma, Code to Canvas, Code Connect, and design system rules”
source ↗“iOS app-building plugin supports SwiftUI implementation, refactors, performance, and debugging”
source ↗“Web app-building plugin supports deployment, UI, payments, and database workflows”
source ↗“Notion plugin supports planning, research, meetings, and knowledge capture”
source ↗“'Sign in with ChatGPT' is rolling out in beta for supported plugins and partner sites like Airtable, GitLab, HubSpot, Notion, Supabase, and Vercel”
source ↗“Expo plugin supports Expo/React Native apps, SDK upgrades, EAS workflows, and Codex Run actions”
source ↗“'/skills' command or typing '$' lets you mention/invoke a skill directly in Codex CLI or IDE extension”
source ↗
Business model
Public plugin/skill catalog and marketplace for Codex with per-skill licenses; the plugins are free but running them requires Codex, which needs a paid ChatGPT plan or API key.
pricing ↗Score trend
How this product’s scores have moved as evidence and verdicts are re-derived — a point per change, not per day.
Try Experimental
Run it in the microterminal →Recorded agent sessions — and a live MCP handshake where the vendor ships one.
Flag
⚑ Flag a verdictThink a verdict is wrong? Opens a prefilled GitHub issue — or use the ⚑ next to any verdict above.
For agents
Agent surface uptime llms.txt 100% (30d, checked every 6h since Sep 8 '26)
