nexu-io/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.
npx skills add https://github.com/nexu-io/codex-slides --skill codex-slides-verification
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.
Take nexu-io/codex-slides-verification 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.