agentsclimarketplace

Codex slides browser

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

🎨 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-browser

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

Compatibility entry point for opening and operating Codex Slides in Codex's in-editor Browser, including scenario selection, Design Files, brand systems, decks, and Play mode. Use when the user asks to open, launch, preview, view, play, inspect, or directly manipulate Codex Slides or a deck without leaving Codex.

SKILL.md

2.7 KB, as published. Nobody here has run it

Codex Slides Browser

This specialized skill remains for compatibility. The canonical codex-slides sibling skill owns the full workflow and portable CLI.

  1. Call open_codex_slides when the MCP tool is available. Otherwise run node ../codex-slides/scripts/codex-slides.mjs open --json '<input>' from this skill directory. Pass projectId when the user named a deck; otherwise omit it for the create workspace. Use view:"scenarios" for the 24-workflow catalog, view:"design-files" plus projectId and optional filePath for project files, or view:"brand-system" plus projectId for the brand editor.
  2. Navigate the returned resource link in the Codex in-editor Browser. Do not stop after printing the URL and do not ask the user to open it manually. Follow browserHandoff.url exactly so slide, panel, version, mode, checkpoint, conversation, and run focus are preserved.
  3. For a new deck, always open and verify the home/create screen before any research, outline, or rendering call. Submit the topic in that UI so it creates a durable project and opens the guided workspace. Use start_project / CLI start-project only if UI submission needs a deterministic fallback, then navigate its project resource immediately.
  4. Keep the Browser visible and operate the checkpoints in order: clarify, outline review, inspiration/style selection, render, deck review. Do not run the entire workflow invisibly in the Codex conversation.
  5. Use direct MCP tools or the canonical skill CLI for deterministic recovery and mutations, then reload or inspect the Browser result.
  6. Verify the visible outcome before reporting completion.

Long Deck Agent, outline, and render operations can continue after navigation. Use start_project_run, retain its runId, and use get_project_run, wait_project_run, or cancel_project_run without closing the Browser.

Use the Browser for scenario/slot selection, @ Design File references, brand system editing, Play from the current slide or the beginning, dual-window presenter mode, speaker notes editing/AI generation, slide navigation, direct on-canvas marking, layout inspection, and other visual interactions. If the Browser capability is unavailable in the current Codex surface, return the resource link and explain that limitation rather than claiming it opened.

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.