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 skills add https://github.com/nexu-io/codex-slides --skill 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.
.codex-plugin/plugin.json must start withthe exact root package.json version plus +codex.. The desktop package must
use the same product version.
CODEX_SLIDES_URL and CODEX_SLIDES_LOG.The local MCP launcher may need to prepare dependencies or a standalone build.
plugin and start a new Codex task so the versioned plugin cache is refreshed.
get_project_run. Wait, cancel itexplicitly, or allow a Deck Agent request to remain in the visible queue.
wait_project_run or reopen its browserHandoff.
terminal runHistory; refresh the plugin/runtime before retrying the task.
cancelled, then continue.
browserHandoff.url; do not reconstruct a project URL.slide, panel, version, mode, checkpoint,conversation, and run.
/?resume=<id>. The continuationquery must survive that redirect.
link opens the Play menu at the correct slide instead of bypassing popup
protection.
a durable render run for the existing project.
/runs/get_project as thecanonical snapshot, then reload the same Browser handoff.
error or whose persistedimage cannot be loaded.
list_design_files; never guess an absolute path.verification. Speaker notes are off-canvas but must remain present in PPTX.
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.
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.
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.
Replace with description of the skill and when Claude should use it.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
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.
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.
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Take nexu-io/codex-slides-known-errors from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
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.