菜单
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.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/nexu-io/codex-slides --skill codex-slides-structured-intake命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
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 Slides or a deck without leaving Codex.
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 brand or template rules, or export PDF/PPTX.
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.
基于 SOC 职业分类
正在显示 SKILL.md
| 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. |
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.
open_codex_slides without a project id and follow its
browserHandoff to the home/create workspace.list_scenarios, then open the selected
scenario deep link. Use product-owned defaults and source slots.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.