Codex marketplace still bundles removed v0-dev skill with outdated API and MCP guidance
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 287
- Forks
- 58
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 17
Description
Problem
The Vercel plugin distributed through the Codex marketplace still includes v0-dev guidance for the older v0 API and MCP authentication. This was encountered while trying to download an existing v0 application's source.
Affected installation: vercel plugin version 0.21.4. The current marketplace source also contains the outdated guidance, so this is not only a local cache issue.
Evidence
The bundled skill teaches:
v0-sdk, version-based downloads usingv0.chats.downloadVersion, andchat.latestVersion.id.- MCP at
https://mcp.v0.devwith a bearer API key.
Current official documentation instead describes:
- v2 downloads:
v0.chats.downloadFiles({ chatId })from thev0package;GET /v2/chats/{chatId}/files/downloadreturns a ZIP. - MCP setup:
https://v0.app/api/mcpwith OAuth; explicitly do not put a v0 API key in MCP configuration. Its documented tool list does not include ZIP download. - Compatibility: v2 cannot operate on older v1 chats. The v1 download operation remains appropriate for those chats, so a blanket method-name replacement would be incorrect.
Meanwhile, upstream removed v0-dev in 7a73b56, but the marketplace package retained it. The v0 SDK repository now has a current SDK skill.
Expected outcome
Please reconcile the Codex marketplace package with the intended source of truth: either retire/redirect the stale skill or update it from current v0 guidance, retaining explicit v1 compatibility and the distinction between API-key downloads and OAuth MCP access.
The packaging issue is in openai/plugins, but that repository has issues disabled. Filing here for the Vercel plugin maintainers to coordinate the marketplace correction. No API download was validated in this investigation; the mismatch was verified against the installed skill, current repository contents, and official documentation.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading plugins/vercel/skills/v0-dev/SKILL.md in the marketplace source, then compare it with the current v0 SDK skill and the linked upstream removal commit. Check the documented v1 and v2 download guidance and MCP setup. Done means the marketplace package is retired, redirected, or updated without losing v1 compatibility or confusing API-key downloads with OAuth MCP access.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- documentation, tooling
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100