codex-slides-browser
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.
git clone --depth 1 https://github.com/nexu-io/codex-slides /tmp/codex-slides-browser && cp -r /tmp/codex-slides-browser/skills/codex-slides-browser ~/.claude/skills/codex-slides-browserSKILL.md
# 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.
Compatibility entry point for scenario-led creation, Design Files, brand systems, inspecting, revising, restyling, and exporting Codex Slides slide decks. Use when a user asks Codex to make a presentation, use project files, edit an existing deck, manage slide structure, apply brand or template rules, or export PDF/PPTX.
Diagnose and recover from Codex Slides plugin, MCP, Browser handoff, local runtime, durable run, project resume, rendering, Design Files, export, and version-contract failures. Use when a tool fails, a run stalls, a project appears stale, or Codex and the Browser disagree.
Compatibility entry point for researching a current topic into a source-backed Markdown brief and turning it into a Codex Slides outline or rendered deck. Use for market, competitive, policy, technical, academic, or other presentation requests that need current facts, figures, comparisons, or citations.
Collect and persist structured presentation requirements for Codex Slides, including scenario choice, audience, page count, language, format, research mode, visual direction, source-file roles, and clarification checkpoints. Use when a new deck request is ambiguous or scenario-led.
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.
Create, research, revise, restyle, present, inspect, and export Codex Slides slide decks from Codex, including scenario workflows, project Design Files, and always-on brand design systems. Use when the user asks for a presentation, PPT/PPTX, slide deck, research brief converted into slides, an existing deck edit, a marked-up slide revision, brand/style controls, project files, or to open and operate Codex Slides in the Codex in-editor Browser.