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 restores, or export.
git clone --depth 1 https://github.com/nexu-io/codex-slides /tmp/codex-slides-verification && cp -r /tmp/codex-slides-verification/skills/codex-slides-verification ~/.claude/skills/codex-slides-verificationSKILL.md
# Codex Slides Verification Use two signals before reporting a presentation task complete: 1. Read canonical project state with `get_project`, and read a named durable job with `get_project_run` or `wait_project_run` when a `runId` was returned. 2. Follow the returned `browserHandoff` and inspect the exact visible result in the Codex in-editor Browser. ## Verification sequence 1. Confirm the project id rather than guessing from a similar title. 2. For a durable run, require a terminal `complete` status. Treat `error` and `cancelled` as incomplete; a timed-out wait leaves the run active. 3. Confirm the expected page count, changed slide indexes, rendered images, transitions, speaker notes, current workflow stage, and current deck version. 4. Open the exact handoff returned by the mutation. Preserve its `slide`, `panel`, `version`, `mode`, `conversation`, `checkpoint`, and `run` query parameters. 5. In Browser, confirm the intended slide or panel is focused and the visible result matches the request. Do not treat a JSON response alone as visual QA. 6. Export only after the current or explicitly selected version passes review. If the in-editor Browser is unavailable, use the project state and persisted slide-image endpoints as structural evidence, return the exact handoff URL, and state that visible Browser verification remains outstanding. For cross-surface changes, also verify that refreshing or reopening the same project preserves the run result and deep-link focus.
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 Slides or a deck without leaving Codex.
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 brand or template rules, or export PDF/PPTX.
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.
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, comparisons, or citations.
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 scenario-led.
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 into slides, an existing deck edit, a marked-up slide revision, brand/style controls, project files, or to open and operate Codex Slides in the Codex in-editor Browser.