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.
SkillScore87Maintained
Automatic
◆Marketing & Content pack
Last verified 8/16/2026
What it changes
Passed 19 of 22 test cases with the skill, and 12 of 22 without it.
Without skill57%
With skill87%
Checks it passed that the model alone missed
Specifies start_project as the deterministic fallback tool
Directs opening the scenario deep link returned by list_scenarios
Directs following the clarification handoff returned by start_project
and 5 more in the full report
7 fixed13 passed either way3 still failing0 broke
Pass-rate lift
+30 pp
Tokens
-20%
Agent turns
0%
Response time
-46%
Model gemini-3.6-flashMeasured 8/16/2026v120 of 23 cases passed with skill · 22 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 7
Prompt
I found a matching workflow preset in Codex Slides using `list_scenarios`. What is the immediate next step to open that specific scenario?
What was checked, without and with the skill
Checked
Without skill
With skill
Directs opening the scenario deep link returned by list_scenarios
Missed
Passed
case-12 · 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.md33 linessingle file
Codex Slides Structured Intake
The Codex Slides Browser owns the canonical intake form. Structured intake must
produce one durable project and one shared clarification state, not a separate
chat-only questionnaire.
Flow
Call open_codex_slides without a project id and follow its
browserHandoff to the home/create workspace.
When a workflow preset fits, call list_scenarios, then open the selected
scenario deep link. Use product-owned defaults and source slots.
Submit the user's topic and available files in the Browser. Assign every
uploaded file its scenario role; do not flatten datasets, source decks,
brand assets, and visual references into one undifferentiated list.
Let the product create the durable project before clarification. Keep the
clarification checkpoint visible and persist answers in project workflow
state.
Ask only questions that materially change the result: audience, purpose,
page count, language, aspect, research depth, evidence constraints, and
visual direction. Use recommendations already present in the form.
Continue through outline and inspiration checkpoints in the same Browser
project. Do not call the unattended create_deck path unless the user asked
for a headless run.
If Browser submission is unavailable, use start_project as the deterministic
fallback, immediately follow its clarification handoff, and keep later choices
attached to that same project id. get_onboarding_questions may help formulate
the intake, but its output is not a second source of truth.
When a durable outline or render job is useful, call start_project_run, keep
its runId, and use wait_project_run or cancel_project_run without closing
the Browser workspace.