Install any skill in seconds. Free to start, no credit card required.
Get Started Free →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.
.claude/skills/nexu-io-codex-slides-verification/SKILL.md| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-02 | ✗→✓ | ▲ Improved | 153% | 0% |
| case-05 | ✗→✓ | ▲ Improved | -69% | 0% |
| case-08 | ✗→✓ | ▲ Improved | -54% | 0% |
| case-10 | ✗→✓ | ▲ Improved | -35% | 0% |
| case-11 | ✗→✓ | ▲ Improved | -47% | 0% |
Use two signals before reporting a presentation task complete:
get_project, and read a named durable jobwith get_project_run or wait_project_run when a runId was returned.
browserHandoff and inspect the exact visible result inthe Codex in-editor Browser.
complete status. Treat error andcancelled as incomplete; a timed-out wait leaves the run active.
transitions, speaker notes, current workflow stage, and current deck version.
slide,panel, version, mode, conversation, checkpoint, and run query parameters.
result matches the request. Do not treat a JSON response alone as visual QA.
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.
Other measured skills in the registry, with their headline benchmark lift.