---
name: Codex Slides Browser
slug: codex-slides-browser
category: Automation
description: Codex Slides Browser opens and controls Codex Slides in the in-editor Browser for scenario selection, design files, brand systems, Play mode, and slide inspection. Use it when you need to view or manipulate a deck without leaving Codex.
github: "https://github.com/nexu-io/codex-slides/tree/master/skills/codex-slides-browser"
language: TypeScript
stars: 838
forks: 69
install: "npx degit https://github.com/nexu-io/codex-slides/tree/master/skills/codex-slides-browser ~/.claude/skills/codex-slides-browser"
installs_to: ~/.claude/skills/codex-slides-browser
source_path: skills/codex-slides-browser/SKILL.md
collection_size: 7
category_size: 1523
collection_url: "https://dirskills.com/collections/nexu-io/codex-slides"
added: 2026-08-22T05:22:00.818Z
last_synced: 2026-08-22T05:22:00.818Z
canonical_url: "https://dirskills.com/skills/codex-slides-browser"
---

# Codex Slides Browser

Codex Slides Browser opens and controls Codex Slides in the in-editor Browser for scenario selection, design files, brand systems, Play mode, and slide inspection. Use it when you need to view or manipulate a deck without leaving Codex.

**Install:**

```bash
npx degit https://github.com/nexu-io/codex-slides/tree/master/skills/codex-slides-browser ~/.claude/skills/codex-slides-browser
```

## README

# 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.