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.
SkillScore38Maintained
Automatic
◆Marketing & Content pack
Last verified 8/16/2026
What it changes
Passed 4 of 10 test cases with the skill, and 2 of 10 without it.
Without skill17%
With skill38%
Checks it passed that the model alone missed
Routes the task to codex-slides-verification
Starts the execution via start_project_run or run-start
Passes the retrieved ID as projectTemplateId rather than template
and 8 more in the full report
6 fixed3 passed either way14 still failing1 broke
Pass-rate lift
+21 pp
Tokens
+99%
Agent turns
0%
Response time
-52%
Model gemini-3.6-flashMeasured 8/16/2026v19 of 24 cases passed with skill · 10 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 6
Prompt
We just completed a major automated deck restyle and layout update across all 12 slides. What workflow skill should perform the visual quality check and slide verification?
What was checked, without and with the skill
Checked
Without skill
With skill
Routes the task to codex-slides-verification
Missed
Passed
Avoids attempting visual deck verification without the specialized sibling skill
Passed
Passed
case-22 · gemini-3.6-flash · 8/16/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md206 lines5 filesincludes scripts
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:
Call open_codex_slides / CLI openwithout 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.
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.
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.
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.
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.
Do not call deep_research, create_outline, rank_inspiration,
render_deck, or create_deck before opening the Browser for a normal deck
request. Do not default to create_deck; it is the explicit unattended fast
path. A user's request such as "make a six-slide deck and show me" still uses
the Browser-first guided flow unless they specifically ask Codex to finish it
in the background without checkpoints.