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.
Profile →npx skills add nexu-io/codex-slides --skill codex-slides-verification --agent codex
Same command for any agent — swap --agent for claude-code, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 s
- Verification sequence
What does the codex-slides-verification skill do?
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.
How do I install it?
Run `npx skills add nexu-io/codex-slides --skill codex-slides-verification --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From nexu-io/codex-slides, a repository with 753 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.