mcpbeat Sign in

Codex Slides Known Errors Skill for Codex

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.

782 tokens
context cost
the whole folder, loaded on every use
2
files
instructions only
0
copies elsewhere
how many repositories repackaged it
748
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/nexu-io/codex-slides --skill codex-slides-known-errors

The instruction itself

6 sections, as written by the author

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.

Other skills for the same job

different authors, same section of the catalogue
Skill Creator
by anthropics
vendor ×10

Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.

56k tokens scripts
Skill Creator
by vercel-labs
vendor ×10

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.

12k tokens scripts
Skill Creator
by JayZeeDesign
×9

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.

10k tokens scripts
Template Skill
by JayZeeDesign
×7

Replace with description of the skill and when Claude should use it.

35 tokens
Dispatching Parallel Agents
by ZhanlinCui
×5

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

2k tokens
Skill Development
by anthropics
vendor ×4

This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.

9k tokens
Find Skills
by sanity-io
vendor ×4

Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.

1k tokens
Writing Skills
by ZhanlinCui
×4

Use when creating new skills, editing existing skills, or verifying skills work before deployment

26k tokens scripts

How to use it

Copy the folder

Take nexu-io/codex-slides-known-errors from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.