Skip to content
Skills Library
Documents & office · Planning

codex-slides-structured-intake

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

Licence
MIT
Last repository change
21.07.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 21.07.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

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.

Original author 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.

How it works

  1. Flow
Original SKILL.md headings · 35 lines, 246 words
SKILL.md preview
---
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.
Files in this package (2)
  • SKILL.md 2 KB
  • agents/openai.yaml 1 KB

Versions

The database has no other skills named codex-slides-structured-intake.

Database snapshot: 13.11.2026 · package version 546328fa4399 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 86codex-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…
  • 100codex-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…
  • 90slides
    Turns bullet points, research, or structured content into a browser-based Reveal.js slide deck. Use when the user asks to create slides, a presentation, a deck, a slideshow, or says "present this", "turn this into slides", "make a deck", or mentions keynote, powerpoint, or reveal.
  • 100p-md-to-slides
    Convert a structured Markdown deck source into a styled Google Slides presentation. Use this skill when the user has a slide.md file (or wants to write one) and wants Google Slides output — talks, LT decks, lecture slides, conference presentations, internal explainers. Trigger…
  • 100presentation-creator
    Use when asked to create a presentation, pitch deck, or slides from a topic and audience, or to format supplied source items into a 16:9 HTML slide deck. Not for PowerPoint files.
  • 100slides-artifact
    Use when the user asks to create, edit, or review slides or a presentation (PowerPoint or Google Slides), including when the task clearly calls for an audience-ready slide deck. Also use to answer questions that require inspecting an existing deck; not for general presentation…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.