agentsclimarketplace

Codex slides verification

Skill nexu-io/codex-slides/skills/codex-slides-verification

🎨 Open-source AI slide studio inside Codex: image-native decks, every slide a full visual canvas. ⚡ 10+ high-quality slides in ~4–5 minutes — Fast mode renders every page in parallel. 🔍 Watch the whole chain live: research → outline → style → render → edit → present → export PDF/PPTX. 🖥️ Browser-first · zero API keys · durable projects.

Install
npx -y skills add nexu-io/codex-slides --skill codex-slides-verification

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 26 days oldThe repository was created 26 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.

What its author says it does

Copied from the file, not written here

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.

SKILL.md

1.8 KB, as published. Nobody here has run it

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.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.