/codex-slides-structured-intake
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
$ npx -y skills add nexu-io/codex-slides --skill codex-slides-structured-intake --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/codex-slides-structured-intake
Context preview
The summary Claude sees to decide when to auto-load this skill.
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
SKILL.md
codex-slides-structured-intake.SKILL.mdname: codex-slides-structured-intake
description: 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.
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
1. Call `open_codex_slides` without a project id and follow its `browserHandoff` to the home/create workspace. 2. When a workflow preset fits, call `list_scenarios`, then open the selected scenario deep link. Use product-owned defaults and source slots. 3. 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. 4. Let the product create the durable project before clarification. Keep the clarification checkpoint visible and persist answers in project workflow state. 5. 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. 6. 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.
Read more
name: codex-slides-structured-intake description: 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.
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
1. Call `open_codex_slides` without a project id and follow its `browserHandoff` to the home/create workspace. 2. When a workflow preset fits, call `list_scenarios`, then open the selected scenario deep link. Use product-owned defaults and source slots. 3. 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. 4. Let the product create the durable project before clarification. Keep the clarification checkpoint visible and persist answers in project workflow state. 5. 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. 6. 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.
🎨 Open-source AI slide studio inside Codex: image-native decks, every slide a full visual canvas. ⚡ 10+ high-quality slides in ~4–5 minutes — Fast mode renders every page in parallel. 🔍 Watch the whole chain live: research → outline → style → render → edit → present → export PDF/PPTX. 🖥️ Browser-first · zero API keys · durable projects.
Repo: nexu-io/codex-slides
Other skills on codex-slides.
- /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
Open skill - /codex-slides-deck
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
Open skill - /codex-slides-known-errors
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.
Open skill - /codex-slides-research
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,
Open skill - /codex-slides-verification
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
Open skill - /codex-slides
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
Open skill

