codex-slides-structured-intake

$npx mdskill add nexu-io/codex-slides/codex-slides-structured-intake

Collects and persists structured presentation requirements for Codex Slides.

  • Solves ambiguous or scenario-led deck requests by gathering structured requirements.
  • Depends on Codex Slides Browser, list_scenarios, and deep links.
  • Uses scenario presets and product defaults to guide requirement collection.
  • Delivers a durable project with persisted clarification state in the workflow.

SKILL.md

.github/skills/codex-slides-structured-intakeView on GitHub ↗
---
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.

More from nexu-io/codex-slides

SkillDescription
codex-slidesCreate, 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.
codex-slides-browserCompatibility 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 Slides or a deck without leaving Codex.
codex-slides-deckCompatibility 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 brand or template rules, or export PDF/PPTX.
codex-slides-known-errorsDiagnose 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.
codex-slides-researchCompatibility 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, comparisons, or citations.
codex-slides-verificationVerify 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 restores, or export.