# Codex Slides

Create, research, revise, restyle, present, inspect, and export Codex Slides slide...

- Repository: https://github.com/nexu-io/codex-slides (966 stars)
- Category: Design
- License: MIT
- Last updated: 2026-07-21
- Runs scripts: yes, review before use

## Install

Claude Code: `npx skills add nexu-io/codex-slides --skill codex-slides -g -a claude-code -y`
Codex: `npx skills add nexu-io/codex-slides --skill codex-slides -g -a codex -y`
Cursor: `npx skills add nexu-io/codex-slides --skill codex-slides -g -a cursor -y`
Gemini CLI: `npx skills add nexu-io/codex-slides --skill codex-slides -g -a gemini-cli -y`

## Description

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.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Codex Slides

Run Codex Slides as an interactive product inside Codex. The live Browser
workspace is the primary experience; MCP and the bundled CLI are transports
for opening the workspace and performing deterministic operations, not a reason
to hide the presentation workflow in a long-running Codex turn.

## Browser-first default

For every new deck request, unless the user explicitly asks for a headless,
unattended, one-call, or CLI-only run:

1. Call `open_codex_slides` / CLI `open` **without** a project id, immediately
   navigate the returned URL in Codex's in-editor Browser, and verify that the
   Codex Slides home/create screen is visible.
2. Keep the Browser open. Enter the user's request in the home composer, attach
   or assign source files in the UI, and submit it there. This creates a durable
   project before clarification starts. If UI submission is not reliable, use
   `start_project` / CLI `start-project` only as a deterministic fallback, then
   navigate its returned project URL immediately.
3. Continue in the live project workspace. Let Codex Slides show and own each
   checkpoint: requirements/clarifying questions, research progress, editable
   outline confirmation, visual-inspiration or style selection, and rendering.
   Answer or manipulate each step in the Browser; when a choice materially
   changes the result and the user's prompt does not resolve it, leave that
   checkpoint visible and ask the user.
4. During research and rendering, keep the project workspace visible so the
   user sees progress and can steer. Do not leave Codex showing only a generic
   "working" message while a hidden tool completes the whole deck.
5. After rendering, inspect the deck in the same Browser workspace. Use its
   agent composer, slide controls, mark mode, Play, Design Files, and brand
   system for follow-up work. Export only after visual review.

The rest: https://github.com/nexu-io/codex-slides/blob/HEAD/skills/codex-slides/SKILL.md