Skip to content
FunCoding

Search

Search docs, Skills and MCP

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.

浏览器自动化927skills/codex-slides-known-errors/SKILL.md

Install

Send this to Claude Code, Codex or Cursor. The agent checks the Skill for safety first and installs it only after you confirm.

读取 https://funcoding.ai/skills/nexu-io/codex-slides/codex-slides-known-errors/install.md ,按里面的步骤帮我安装这个 Skill。

SKILL.md

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.

Similar Skills

webapp-testing
anthropics/skills180k

webapp-testing

Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

Browser automation

browser-testing-with-devtools
addyosmani/agent-skills103k

browser-testing-with-devtools

Tests in real browsers via Chrome DevTools MCP. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data. Requires the chrome-devtools MCP server to be configured.

Browser automation

webapp-testing
ComposioHQ/awesome-claude-skills77k

webapp-testing

Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

Browser automation

browser
code-yeongyu/oh-my-openagent70k

browser

Drives a real browser through the omowright library from the js eval kernel: sites the user is already signed into, forms and clicks, JS-rendered pages, screenshots, web QA, extension popups, a human handoff for login, CAPTCHA or OTP, and a browser you own for scraping, bot-scored targets, network capture and QA traces. Use for any interactive browser task; not for a plain search or an unblocked static fetch.

Browser automation

agent-browser
shanraisshan/claude-code-best-practice67k

agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.

Browser automation

cherry-regression-test
CherryHQ/cherry-studio52k

cherry-regression-test

Run Cherry Studio critical-path system regression tasks through the repository-owned Playwright E2E workflow. Use for full regression, release acceptance, development-branch system validation, or a named cherry-regression-test task on GitHub-hosted macOS and Windows runners.

Browser automation