Update Codex Plugin
Update Remotion's published Codex and ChatGPT directory plugin to a released Remotion version. Prepare the ZIP from the official Codex plugin repository, preserve its listing metadata, and upload and publish through OpenAI Platform.
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Update Codex Plugin when an AI agent needs a reusable SKILL.md workflow for this job: Update Remotion's published Codex and ChatGPT directory plugin to a released Remotion version. Prepare the ZIP from the official Codex plugin repository, preserve its listing metadata, and upload and publish through OpenAI Platform.
When not to use it
Skip Update Codex Plugin when the task is outside the coding category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/update-codex-plugin # Save SKILL.md to ~/.claude/skills/update-codex-plugin/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/update-codex-plugin/SKILL.md. For a shared project, commit the folder at .claude/skills/update-codex-plugin/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Update Codex Plugin skill for this task: Use Update Codex Plugin when this documented workflow matches the task. Confirm any required inputs or files before making changes.
What supports this recommendation?
71/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 77/100
- Practical detail
- 68/100
- Source evidence
- 63/100
- Source signals
- 72/100
Model compatibility evidence
- claudeuntested
No model-specific signal or recorded compatibility test was found.
- chatgptinferred
The skill text mentions ChatGPT or a closely associated term. This is keyword-derived compatibility; no hands-on model test is recorded.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# Update the Codex plugin
Update the existing public Remotion plugin, whose identity is `plugins~Plugin_efd07789186881918253a50acfc32762`.
- Dashboard: https://platform.openai.com/plugins/manage/plugins~Plugin_efd07789186881918253a50acfc32762 - Public listing: https://chatgpt.com/plugins/plugins~Plugin_efd07789186881918253a50acfc32762 - Release source: https://github.com/remotion-dev/codex-plugin
The monorepo release pipeline updates this GitHub repository but does not update the public directory. `codex plugin add` and marketplace upgrades manage local installations, not the public listing. Do not use the old `packages/codex-plugin` build directory, `openai/plugins`, or the portable `cursor-plugin` package for this upload.
As checked on 2026-10-08, OpenAI documents a dashboard ZIP upload workflow, and the available CLI has no public-directory publishing command. Use browser tools for this part. Prefer a documented publishing API if one becomes available; do not replay private dashboard requests or extract browser credentials. Current reference: [OpenAI plugin submission](https://developers.openai.com/plugins/deploy/submission).
## Inspect the current release
Use the browser's signed-in OpenAI Platform session. Confirm the Remotion organization and the existing plugin identity. The dashboard's **Publication Version** is authoritative; the local plugin cache can lag behind it.
Read the version selector and review state before uploading. If the requested version is already published, report that. If its draft or review already exists, continue that version instead of making a duplicate. Do not cancel another active review just to upload again.
Select the **Published** version under **Metadata & Skills**, then use **More plugin actions → Download release ZIP**. Use the actual downloaded file path. This is the baseline for preserving listing text, branding, and publication settings. An installed cache is not a substitute for the published package.
## Prepare the ZIP
Run from the monorepo root:
```bash python3 .agents/skills/update-codex-plugin/scripts/prepare-release.py \ --published-zip /absolute/path/to/downloaded-release.zip ```
By default, the helper resolves the latest stable Remotion GitHub release. To use a user-requested release, add `--version 4.0.534`. It requires `gh` and Python 3, fetches the corresponding tag from `remotion-dev/codex-plugin`, pins its commit, and creates a temporary staging directory and upload ZIP outside the checkout. It does not publish, install, or modify the monorepo.
The helper uses the released package and preserves the published `interface`, assigned `id`, and OpenAI `extensions`, including referenced listing assets. Inspect its JSON report, particularly `preserved_manifest_differences`. Keep those overrides for a skills update; change them only when the task includes a listing change. If the source package structure has changed incompatibly, adapt the helper before uploading instead of silently dropping components.
Check the reported source commit, version, skill names, and ZIP path. The helper validates the staged manifest, skill layout, release versions, and preserved listing assets. With the monorepo dependencies installed, validate relative links in the staged skills from the monorepo root:
```bash SKILLS_ROOT="/absolute/path/to/staged/remotion/skills" bun packages/skills/scripts/validate-links.ts ```
Also run the handwritten checks for the monorepo's Codex and portable plugin builds:
```bash bun run --cwd packages/agent-plugin test ```
Fix packaging findings before uploading. These local structural checks do not replace the dashboard's metadata and skill review.
## Upload and publish in the browser
An instruction to update this published plugin covers its normal upload and publication workflow. Honor narrower requests such as preparing a ZIP, creating a skill, or uploading a draft; those alone do not authorize publication.
1. Open the existing plugin and click **Upload new version**, **Upload plugin to make changes**, or **Upload plugin to fix issues**, whichever the dashboard shows. 2. In **Upload new version**, keep the existing verified Remotion developer identity. Choose the helper's ZIP using the browser tool's file-upload API, reading its upload documentation first. Choosing the file can start the upload immediately; inspect the result before clicking **Upload plugin** or retrying. If Chrome's extension upload requires **Allow access to file URLs**, the native picker also works: select the correct Chrome tab through the native app tool, click **Choose file**, press Command-Shift-G, read the new accessibility state, set the path field to the exact ZIP, press Return, verify the selected filename, then click **Open**. Do not change extension permissions just for this fallback. 3. Confirm the new version under **Metadata & Skills**. Read metadata and skill check results for that version, not the older published version. Refresh the browser state after actions; do not reuse stale element indices. 4. Follow the displayed review workflow. Read findings before deciding whether they block submission. A skill can show **Needs attention** while the version is **Approved** and **Ready to publish**; a warning alone does not establish that review failed. If a new ZIP is needed, fix the staged package and recreate it, preserving the release's provenance. Do not keep uploading the same ZIP to retry pending scans. 5. When the requested version is approved and publication is authorized, select **Publish plugin**. If policy attestations include accepting legal terms, obtain the confirmation required by the active browser tool before accepting them. Do not claim unperformed tests or invent review information. 6. Verify **Publication Version** shows the target version as **Published**. A selected draft, successful upload, approval, or GitHub tag does not establish publication. Save browser evidence using the active tool's supported method.
Scans and human review may outlast the current turn. Report the exact version, state, findings, and dashboard URL; keep the dashboard available for follow-up. Only set up a scheduled follow-up when the user asks for one. On an uncertain upload result, inspect the version list before retrying.
Finish with the prepared or published version, source commit, validation result, and any remaining dashboard step. Clearly distinguish **prepared**, **uploaded**, **under review**, **approved**, and **published**.
Intended uses
- Use Update Codex Plugin when this documented workflow matches the task.
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.