agentsclimarketplace

Codex slides structured intake

Skill nexu-io/codex-slides/skills/codex-slides-structured-intake

🎨 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.

Install
npx -y skills add nexu-io/codex-slides --skill codex-slides-structured-intake

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 26 days oldThe repository was created 26 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.

What its author says it does

Copied from the file, not written here

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.

SKILL.md

2.0 KB, as published. Nobody here has run it

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.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.