Codex Slides Known Errors logo

Codex Slides Known Errors

Organization
nexu-io
codex-slides-known-errors

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.

Overview

Publishernexu-io
Repositorycodex-slides
Skill namecodex-slides-known-errors
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 Known Errors 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-known-errors
  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-known-errors .claude/skills/codex-slides-known-errors
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Codex Slides Known Errors 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 Known Errors 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 Known Errors 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 Known Errors

Classify the failure before retrying. Preserve the same project id and run id; do not recreate a deck merely because a Browser tab closed or a wait timed out.

Runtime and installation

  • Plugin version contract fails: .codex-plugin/plugin.json must start with the exact root package.json version plus +codex.. The desktop package must use the same product version.
  • App is unreachable: inspect CODEX_SLIDES_URL and CODEX_SLIDES_LOG. The local MCP launcher may need to prepare dependencies or a standalone build.
  • Installed skill or tool inventory looks stale: reinstall/upgrade the plugin and start a new Codex task so the versioned plugin cache is refreshed.

Durable runs

  • Another run is active: inspect it with get_project_run. Wait, cancel it explicitly, or allow a Deck Agent request to remain in the visible queue.
  • Wait timed out: the run was not cancelled. Continue with wait_project_run or reopen its browserHandoff.
  • Run id is missing after completion: this indicates an old runtime without terminal runHistory; refresh the plugin/runtime before retrying the task.
  • Run is stopping: do not start a conflicting render. Poll until it becomes cancelled, then continue.

Browser handoff and project resume

  • Use the exact returned browserHandoff.url; do not reconstruct a project URL.
  • Keep all focus parameters: slide, panel, version, mode, checkpoint, conversation, and run.
  • A clarify/research project may route through /?resume=<id>. The continuation query must survive that redirect.
  • Presenter mode needs a user gesture for its second window. A presenter deep link opens the Play menu at the correct slide instead of bypassing popup protection.

Rendering and project state

  • A partially rendered or paused deck is resumable. Read the project and start a durable render run for the existing project.
  • If Codex state and Browser state differ, read /runs/get_project as the canonical snapshot, then reload the same Browser handoff.
  • Do not report success for slides whose status is error or whose persisted image cannot be loaded.

Design Files and export

  • Resolve Design Files through list_design_files; never guess an absolute path.
  • Keep project files distinct from staged materials.
  • Export the current or explicitly selected immutable version only after visual verification. Speaker notes are off-canvas but must remain present in PPTX.

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 Known Errors AI skill do?

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.

Why use Codex Slides Known Errors on TypingMind?

Because you install it once and use it with any model. Codex Slides Known Errors 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 Known Errors in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/nexu-io/codex-slides/tree/master/skills/codex-slides-known-errors. 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 Known Errors?

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 Known Errors?

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

Is the Codex Slides Known Errors 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 👇