Codex Slides Verification Skill for Codex
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.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/nexu-io/codex-slides --skill codex-slides-verificationThe instruction itself
2 sections, as written by the authorCodex Slides Verification
Use two signals before reporting a presentation task complete:
- 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.
- Follow the returned
browserHandoffand inspect the exact visible result in
the Codex in-editor Browser.
Verification sequence
- Confirm the project id rather than guessing from a similar title.
- For a durable run, require a terminal
completestatus. Treaterrorand
cancelled as incomplete; a timed-out wait leaves the run active.
- Confirm the expected page count, changed slide indexes, rendered images,
transitions, speaker notes, current workflow stage, and current deck version.
- Open the exact handoff returned by the mutation. Preserve its
slide,
panel, version, mode, conversation, checkpoint, and run query
parameters.
- 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.
- 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.
Other skills for the same job
different authors, same section of the catalogue
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
Use when implementing any feature or bugfix, before writing implementation code
Use when you have a spec or requirements for a multi-step task, before touching code
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.
| Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases.
Official Opentrons Protocol API for OT-2 and Flex robots. Use when writing protocols specifically for Opentrons hardware with full access to Protocol API v2 features. Best for production Opentrons protocols, official API compatibility. For multi-vendor automation or broader equipment control use pylabrobot.
How to use it
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.