Skip to content
FunCoding

Search

Search docs, Skills and MCP

codex-slides-verification

Verify that Codex Slides changes are durably reflected in project state and visibly reflected in the exact Codex Browser slide, panel, version, checkpoint, or presentation surface. Use after creation, rendering, editing, restyling, mark edits, speaker-note changes, version restores, or export.

浏览器自动化927skills/codex-slides-verification/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-verification/install.md ,按里面的步骤帮我安装这个 Skill。

SKILL.md

Codex Slides Verification

Use two signals before reporting a presentation task complete:

  1. Read canonical project state with get_project, and read a named durable job with get_project_run or wait_project_run when a runId was returned.
  2. Follow the returned browserHandoff and inspect the exact visible result in the Codex in-editor Browser.

Verification sequence

  1. Confirm the project id rather than guessing from a similar title.
  2. For a durable run, require a terminal complete status. Treat error and cancelled as incomplete; a timed-out wait leaves the run active.
  3. Confirm the expected page count, changed slide indexes, rendered images, transitions, speaker notes, current workflow stage, and current deck version.
  4. Open the exact handoff returned by the mutation. Preserve its slide, panel, version, mode, conversation, checkpoint, and run query parameters.
  5. In Browser, confirm the intended slide or panel is focused and the visible result matches the request. Do not treat a JSON response alone as visual QA.
  6. Export only after the current or explicitly selected version passes review.

If the in-editor Browser is unavailable, use the project state and persisted slide-image endpoints as structural evidence, return the exact handoff URL, and state that visible Browser verification remains outstanding.

For cross-surface changes, also verify that refreshing or reopening the same project preserves the run result and deep-link focus.

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