/codex-slides-known-errors
Diagnose and recover from Codex Slides plugin, MCP, Browser handoff, local runtime, durable run, project resume, rendering, Design Files, export, and version-contract failures. Use when a tool fails, a run stalls, a project appears stale, or Codex and the Browser disagree.
$ npx -y skills add nexu-io/codex-slides --skill codex-slides-known-errors --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/codex-slides-known-errors
Context preview
The summary Claude sees to decide when to auto-load this skill.
Diagnose and recover from Codex Slides plugin, MCP, Browser handoff, local runtime, durable run, project resume, rendering, Design Files, export, and version-contract failures. Use when a tool fails, a run stalls, a project appears stale, or Codex and the Browser disagree.
SKILL.md
codex-slides-known-errors.SKILL.mdname: codex-slides-known-errors
description: Diagnose and recover from Codex Slides plugin, MCP, Browser handoff, local runtime, durable run, project resume, rendering, Design Files, export, and version-contract failures. Use when a tool fails, a run stalls, a project appears stale, or Codex and the Browser disagree.
Codex Slides Known Errors
Classify the failure before retrying. Preserve the same project id and run id; do not recreate a deck merely because a Browser tab closed or a wait timed out.
Runtime and installation
- **Plugin version contract fails:** `.codex-plugin/plugin.json` must start with
the exact root `package.json` version plus `+codex.`. The desktop package must use the same product version.
- **App is unreachable:** inspect `CODEX_SLIDES_URL` and `CODEX_SLIDES_LOG`.
The local MCP launcher may need to prepare dependencies or a standalone build.
- **Installed skill or tool inventory looks stale:** reinstall/upgrade the
plugin and start a new Codex task so the versioned plugin cache is refreshed.
Durable runs
- **Another run is active:** inspect it with `get_project_run`. Wait, cancel it
explicitly, or allow a Deck Agent request to remain in the visible queue.
- **Wait timed out:** the run was not cancelled. Continue with
`wait_project_run` or reopen its `browserHandoff`.
- **Run id is missing after completion:** this indicates an old runtime without
terminal `runHistory`; refresh the plugin/runtime before retrying the task.
- **Run is stopping:** do not start a conflicting render. Poll until it becomes
`cancelled`, then continue.
Browser handoff and project resume
- Use the exact returned `browserHandoff.url`; do not reconstruct a project URL.
- Keep all focus parameters: `slide`, `panel`, `version`, `mode`, `checkpoint`,
`conversation`, and `run`.
- A clarify/research project may route through `/?resume=<id>`. The continuation
query must survive that redirect.
- Presenter mode needs a user gesture for its second window. A presenter deep
link opens the Play menu at the correct slide instead of bypassing popup protection.
Rendering and project state
- A partially rendered or paused deck is resumable. Read the project and start
a durable `render` run for the existing project.
- If Codex state and Browser state differ, read `/runs`/`get_project` as the
canonical snapshot, then reload the same Browser handoff.
- Do not report success for slides whose status is `error` or whose persisted
image cannot be loaded.
Design Files and export
- Resolve Design Files through `list_design_files`; never guess an absolute path.
- Keep project files distinct from staged materials.
- Export the current or explicitly selected immutable version only after visual
verification. Speaker notes are off-canvas but must remain present in PPTX.
Read more
name: codex-slides-known-errors description: Diagnose and recover from Codex Slides plugin, MCP, Browser handoff, local runtime, durable run, project resume, rendering, Design Files, export, and version-contract failures. Use when a tool fails, a run stalls, a project appears stale, or Codex and the Browser disagree.
Codex Slides Known Errors
Classify the failure before retrying. Preserve the same project id and run id; do not recreate a deck merely because a Browser tab closed or a wait timed out.
Runtime and installation
- **Plugin version contract fails:** `.codex-plugin/plugin.json` must start with
the exact root `package.json` version plus `+codex.`. The desktop package must use the same product version.
- **App is unreachable:** inspect `CODEX_SLIDES_URL` and `CODEX_SLIDES_LOG`.
The local MCP launcher may need to prepare dependencies or a standalone build.
- **Installed skill or tool inventory looks stale:** reinstall/upgrade the
plugin and start a new Codex task so the versioned plugin cache is refreshed.
Durable runs
- **Another run is active:** inspect it with `get_project_run`. Wait, cancel it
explicitly, or allow a Deck Agent request to remain in the visible queue.
- **Wait timed out:** the run was not cancelled. Continue with
`wait_project_run` or reopen its `browserHandoff`.
- **Run id is missing after completion:** this indicates an old runtime without
terminal `runHistory`; refresh the plugin/runtime before retrying the task.
- **Run is stopping:** do not start a conflicting render. Poll until it becomes
`cancelled`, then continue.
Browser handoff and project resume
- Use the exact returned `browserHandoff.url`; do not reconstruct a project URL.
- Keep all focus parameters: `slide`, `panel`, `version`, `mode`, `checkpoint`,
`conversation`, and `run`.
- A clarify/research project may route through `/?resume=<id>`. The continuation
query must survive that redirect.
- Presenter mode needs a user gesture for its second window. A presenter deep
link opens the Play menu at the correct slide instead of bypassing popup protection.
Rendering and project state
- A partially rendered or paused deck is resumable. Read the project and start
a durable `render` run for the existing project.
- If Codex state and Browser state differ, read `/runs`/`get_project` as the
canonical snapshot, then reload the same Browser handoff.
- Do not report success for slides whose status is `error` or whose persisted
image cannot be loaded.
Design Files and export
- Resolve Design Files through `list_design_files`; never guess an absolute path.
- Keep project files distinct from staged materials.
- Export the current or explicitly selected immutable version only after visual
verification. Speaker notes are off-canvas but must remain present in PPTX.
🎨 Open-source AI slide studio inside Codex: image-native decks, every slide a full visual canvas. ⚡ 10+ high-quality slides in ~4–5 minutes — Fast mode renders every page in parallel. 🔍 Watch the whole chain live: research → outline → style → render → edit → present → export PDF/PPTX. 🖥️ Browser-first · zero API keys · durable projects.
Repo: nexu-io/codex-slides
Other skills on codex-slides.
- /codex-slides-browser
Compatibility entry point for opening and operating Codex Slides in Codex's in-editor Browser, including scenario selection, Design Files, brand systems, decks, and Play mode. Use when the user asks to open, launch, preview, view, play, inspect, or directly manipulate Codex
Open skill - /codex-slides-deck
Compatibility entry point for scenario-led creation, Design Files, brand systems, inspecting, revising, restyling, and exporting Codex Slides slide decks. Use when a user asks Codex to make a presentation, use project files, edit an existing deck, manage slide structure, apply
Open skill - /codex-slides-research
Compatibility entry point for researching a current topic into a source-backed Markdown brief and turning it into a Codex Slides outline or rendered deck. Use for market, competitive, policy, technical, academic, or other presentation requests that need current facts, figures,
Open skill - /codex-slides-structured-intake
Collect and persist structured presentation requirements for Codex Slides, including scenario choice, audience, page count, language, format, research mode, visual direction, source-file roles, and clarification checkpoints. Use when a new deck request is ambiguous or
Open skill - /codex-slides-verification
Verify that Codex Slides changes are durably reflected in project state and visibly reflected in the exact Codex Browser slide, panel, version, checkpoint, or presentation surface. Use after creation, rendering, editing, restyling, mark edits, speaker-note changes, version
Open skill - /codex-slides
Create, research, revise, restyle, present, inspect, and export Codex Slides slide decks from Codex, including scenario workflows, project Design Files, and always-on brand design systems. Use when the user asks for a presentation, PPT/PPTX, slide deck, research brief converted
Open skill

