Codex Slides Browser
This specialized skill remains for compatibility. The canonical
codex-slides sibling skill owns the full workflow and portable CLI.
- 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.
- 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.
- 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.
- 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.
- Use direct MCP tools or the canonical skill CLI for deterministic recovery
and mutations, then reload or inspect the Browser result.
- 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.
1---2name: codex-slides-browser3description: 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.4---56# Codex Slides Browser78This specialized skill remains for compatibility. The canonical9`codex-slides` sibling skill owns the full workflow and portable CLI.10111. Call `open_codex_slides` when the MCP tool is available. Otherwise run12 `node ../codex-slides/scripts/codex-slides.mjs open --json '<input>'` from13 this skill directory. Pass `projectId` when the user named a deck;14 otherwise omit it for the create workspace.15 Use `view:"scenarios"` for the 24-workflow catalog,16 `view:"design-files"` plus `projectId` and optional `filePath` for project17 files, or `view:"brand-system"` plus `projectId` for the brand editor.182. Navigate the returned resource link in the Codex in-editor Browser. Do not19 stop after printing the URL and do not ask the user to open it manually.20 Follow `browserHandoff.url` exactly so slide, panel, version, mode,21 checkpoint, conversation, and run focus are preserved.223. For a new deck, always open and verify the home/create screen before any23 research, outline, or rendering call. Submit the topic in that UI so it24 creates a durable project and opens the guided workspace. Use25 `start_project` / CLI `start-project` only if UI submission needs a26 deterministic fallback, then navigate its project resource immediately.274. Keep the Browser visible and operate the checkpoints in order: clarify,28 outline review, inspiration/style selection, render, deck review. Do not run29 the entire workflow invisibly in the Codex conversation.305. Use direct MCP tools or the canonical skill CLI for deterministic recovery31 and mutations, then reload or inspect the Browser result.326. Verify the visible outcome before reporting completion.3334Long Deck Agent, outline, and render operations can continue after navigation.35Use `start_project_run`, retain its `runId`, and use `get_project_run`,36`wait_project_run`, or `cancel_project_run` without closing the Browser.3738Use the Browser for scenario/slot selection, `@` Design File references, brand39system editing, Play from the current slide or the beginning, dual-window40presenter mode, speaker notes editing/AI generation, slide navigation, direct on-canvas41marking, layout inspection, and other visual interactions. If the Browser42capability is unavailable in the current Codex surface, return the resource43link and explain that limitation rather than claiming it opened.
Nexu