Codex Slides Structured Intake logo

Codex Slides Structured Intake

Organization
nexu-io
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.

Overview

Publishernexu-io
Repositorycodex-slides
Skill namecodex-slides-structured-intake
Stars
960
Forks
83
Bundled files
1
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 1 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by nexu-io on GitHub. Read the source before you install it.

Installation

Install the Codex Slides Structured Intake AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/nexu-io/codex-slides/tree/master/skills/codex-slides-structured-intake
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/nexu-io/codex-slides.git /tmp/codex-slides
mkdir -p .claude/skills
cp -r /tmp/codex-slides/skills/codex-slides-structured-intake .claude/skills/codex-slides-structured-intake
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Codex Slides Structured Intake in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Codex Slides Structured Intake on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Codex Slides Structured Intake is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Codex Slides Structured Intake AI 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.

Why use Codex Slides Structured Intake on TypingMind?

Because you install it once and use it with any model. Codex Slides Structured Intake is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Codex Slides Structured Intake in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/nexu-io/codex-slides/tree/master/skills/codex-slides-structured-intake. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Codex Slides Structured Intake?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Codex Slides Structured Intake?

As many as you like. As long as a model supports skills, you can use Codex Slides Structured Intake with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Codex Slides Structured Intake AI skill free?

Yes. It is published on GitHub by nexu-io under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇