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 scenario-led.
Profile →npx skills add nexu-io/codex-slides --skill codex-slides-structured-intake --agent codex
Same command for any agent — swap --agent for claude-code, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 un
- Flow
What does the codex-slides-structured-intake skill do?
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.
How do I install it?
Run `npx skills add nexu-io/codex-slides --skill codex-slides-structured-intake --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From nexu-io/codex-slides, a repository with 753 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.