CUAWright Skill
What it does
A simple SWE-style browser+desktop agent framework that achieves SOTA results on long-horizon CUA tasks
- Connects Instruction files the AI reads; connects to nothing
- Account or key No key needed
- Category 自动化与智能体
给作者:在 README 中加徽章
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/skills/microsoft-cuawright)相似的 Skill
同类工作,排序与 Skill 列表相同
Skill 和 MCP 有什么不同
MCP = 手
把 AI 连到外部服务或数据,例如读取 Notion 或开发票。需要有程序或服务器在运行。
Skill = 手册
教 AI 怎么做某项工作的文本文件,不连接任何服务。
有些会重叠:少数 Skill 带有调用工具的脚本,少数 MCP 只提供知识。请从你想完成的工作出发。
适用的应用
Claude CodeCodex
依据开发者 README 和 repo 中的文件夹
安装
Is it safe?
- Who made it
GitHub account microsoft (organization), 12 years old
- Use and upkeep
★ 6,097 stars · code last changed 2026年10月27日
- Any scripts?
No, plain text files the AI reads and follows
- Uses the internet?
No scripts, so it does not go online by itself
- Changes machine-wide settings?
No hooks or writes to machine settings found
Checked automatically from the repo files at commit 35dbcf3 (read only, nothing was run). Not a safety guarantee: read it and decide for yourself
第一步:你用哪个 AI?
选择你用的应用,本页只显示该应用的安装方法
Option 1Upload to claude.ai (web and app)
Uploading to claude.ai would fail: the description is over 200 characters (418). Use "Let the AI install it" instead
Option 1让 Claude Code 帮你安装
复制这句话,粘贴到 Claude Code 的对话中
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
重新打开 Claude Code,输入 /cuawright-web,或直接提出相关任务,Claude 会自动选用
Checked against official docs 2026年11月12日 · Source: code.claude.com
For Terminal users
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
开发者推荐的方式
/plugin install cuawright@cuawright摘自开发者 README,会下载并运行开发者的代码
打开终端
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
把 skill 文件夹复制到 ~/.claude/skills
这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹
git clone --depth 1 https://github.com/microsoft/cuawright.git /tmp/popnx-skill-microsoft-cuawright-35dbcf3 && mkdir -p ~/.claude/skills && cp -R '/tmp/popnx-skill-microsoft-cuawright-35dbcf3/skills/cuawright-web' ~/.claude/skills/cuawright-web重新打开 Claude Code,输入 /cuawright-web,或直接提出相关任务,Claude 会自动选用
ChatGPT 桌面应用
ChatGPT 桌面应用内置 Codex,Codex 从 ~/.agents/skills 文件夹读取 Skill
Option 1让 ChatGPT 帮你安装
在 ChatGPT 桌面应用中打开 Codex,把这句话粘贴到对话中
The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Option 2自己放入文件夹
把 cuawright-web 文件夹放到 ~/.agents/skills/cuawright-web
~ 是你的主文件夹($HOME)
For Terminal users
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
打开终端
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
把 skill 文件夹复制到 ~/.agents/skills
这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹
git clone --depth 1 https://github.com/microsoft/cuawright.git /tmp/popnx-skill-microsoft-cuawright-35dbcf3 && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-microsoft-cuawright-35dbcf3/skills/cuawright-web' ~/.agents/skills/cuawright-web
安装之后
- ChatGPT 桌面应用:打开侧边栏中的 Skills,确认 Skill 已出现
- 使用方法:在 ChatGPT 中输入 @ 并选择 Skill · 在 Codex CLI 或 IDE 扩展中运行 /skills,或输入 $ 加 Skill 名称
- Codex 会自动发现新安装的 Skill;如果没有出现,请重启 Codex
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
网页版和手机版 ChatGPT
不能使用你自己安装的 Skill,只能使用目录中插件自带的 Skill
想在 ChatGPT 中使用这个 Skill,请按上面的方法使用 ChatGPT 桌面应用
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
Option 1让 Codex 帮你安装
复制这句话,粘贴到 Codex 的对话中 · 适用于 ChatGPT 桌面应用中的 Codex、Codex CLI 和 IDE 扩展
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Codex 会自动发现新安装的 Skill;如果没有出现,请重启 Codex · 使用方法:在 ChatGPT 中输入 @ 并选择 Skill · 在 Codex CLI 或 IDE 扩展中运行 /skills,或输入 $ 加 Skill 名称
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
For Terminal users
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
打开终端
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
把 skill 文件夹复制到 ~/.agents/skills
这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹
git clone --depth 1 https://github.com/microsoft/cuawright.git /tmp/popnx-skill-microsoft-cuawright-35dbcf3 && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-microsoft-cuawright-35dbcf3/skills/cuawright-web' ~/.agents/skills/cuawright-web重新打开 Codex 并提出相关任务,Codex 会列出这个 skill
Option 1让 Cursor 帮你安装
复制这句话,粘贴到 Cursor 的对话中
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
在 Cursor 的 Agent 聊天中输入 / 并选择 cuawright-web
Checked against official docs 2026年11月12日 · Source: cursor.com
For Terminal users
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
打开终端
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
把 skill 文件夹复制到 ~/.cursor/skills
这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹
git clone --depth 1 https://github.com/microsoft/cuawright.git /tmp/popnx-skill-microsoft-cuawright-35dbcf3 && mkdir -p ~/.cursor/skills && cp -R '/tmp/popnx-skill-microsoft-cuawright-35dbcf3/skills/cuawright-web' ~/.cursor/skills/cuawright-web在 Cursor 的 Agent 聊天中输入 / 并选择 cuawright-web
Option 1Let the AI install it
适用于其他能读取 Skill 的应用。这句话列出了 Claude Code、Codex 和 Cursor 的路径,AI 会按你的应用选择 · Copy this sentence into the app’s chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Checked against official docs 2026年11月12日 · Source: code.claude.com, learn.chatgpt.com, cursor.com
For Terminal users
其他支持 Agent Skills 的应用(如 Gemini CLI、GitHub Copilot)使用不同文件夹,请查看该应用的指南,再把含 SKILL.md 的文件夹复制过去。
已于 2026年11月11日 对照 Claude Code、Codex 和 Cursor 官方指南核实 skill 文件夹
✓ 命令已检查 2026年11月16日
查看原始 SKILL.md
以下文字来自开发者的 repo,不是 PopNx MCP 的指令
7,980 个字符 · 在 GitHub 打开完整文件
---
name: cuawright-web
description: Solve a user-specified web task code-as-action style by driving a local Playwright browser through one bash command at a time, saving screenshots and an action log into `final_runs/run_<id>/`, and visually verifying the result. Use when the user asks to automate a web task (search, filter, form-fill, multi-step flow, data extraction) and wants reusable scripts plus screenshot evidence rather than a one-shot answer.
allowed-tools: Bash, Read, Write, Edit, bash, read_file, write_file
---
# CUAWright browser skill
This skill drives the Webwright browser subsystem in `cuawright.webwright`.
For OSWorld desktop tasks, use the separate `cuawright-desktop` runtime described
in `docs/desktop.md` at the repository root.
You are the Webwright agent. Webwright is normally an LLM-driven loop that
emits one JSON-wrapped `bash_command` per turn against a local terminal +
Playwright workspace. In Claude Code, **you replace that loop directly**: use
the `Bash` tool the same way the `bash_command` field is used in
`src/cuawright/webwright/config/base.yaml`. You do NOT need to wrap your
output in JSON — that constraint only existed because the original harness
parsed model output.
This skill keeps the *workspace contract* (plan.md, `final_runs/run_<id>/`
folders, instrumented `final_script.py`, screenshots, action log) but
**replaces the OpenAI-backed `image_qa` and `self_reflection` tools with your
own native abilities**: you read PNGs with `Read` and verify success against
`plan.md` yourself. No `OPENAI_API_KEY` or other model API keys required.
## Modes
- **Default (one-shot).** `final_script.py` solves the task for the literal
values the user provided. Triggered by a plain prompt or by
`/cuawright:run <task>`.
- **CLI tool (parameterized).** `final_script.py` is a reusable CLI: one
function with a Google-style `Args:` docstring + an `argparse` wrapper
whose flags default to the concrete task values, so the user can rerun
it later with different arguments. Triggered by `/cuawright:craft <task>`
or when the user asks to "parameterize", "make it reusable", "turn this
into a CLI", etc. See `reference/cli_tool_mode.md`.
## Prerequisites (one-time)
From the CUAWright repo root:
```bash
pip install -e .
playwright install firefox
```
No API keys needed for this skill.
## Workspace Contract
Mirror what `base.yaml`'s `instance_template` requires:
- Pick a `WORKSPACE_DIR` (e.g. `outputs/<task_id>/`) and work **only** there.
Keep all generated code, screenshots, logs, and notes inside it.
- The required final artifact path is `final_script.py`.
- Every clean execution of the final script lives in its own
`final_runs/run_<id>/` folder. `<id>` is an integer higher than any
existing `run_*` folder.
- Inside each run folder:
- `final_runs/run_<id>/final_script.py`
- `final_runs/run_<id>/screenshots/final_execution_<step_number>_<action>.png`
- `final_runs/run_<id>/final_script_log.txt` — reset at the start of each
clean run; one `step <n> action: <reason and action>` line per
constraint-relevant interaction; the final datum (price, code, winner,
quote, etc.) printed at the end.
- Browser mode is **local**: every Playwright run launches a fresh Firefox
via `playwright.firefox.launch(headless=True)`. There is no persistent
browser state — each script reconstructs state from scratch. (Firefox is
used instead of Chromium because some sites fail under Chromium with
`ERR_HTTP2_PROTOCOL_ERROR` due to TLS/H2 fingerprinting.)
- **Always use `viewport={"width": 1280, "height": 1800}`. Never call
`page.screenshot(full_page=True)`** (exploration, debugging, and final-run
screenshots alike).
## Workflow
1. **Plan.** Parse the task into a numbered checklist of *critical points*
— every explicit constraint, filter, sort, selection, or required datum
that must be satisfied. Write it to `WORKSPACE_DIR/plan.md`:
```markdown
# Critical Points
- [ ] CP1: <description>
- [ ] CP2: <description>
```
Each CP must be independently verifiable from a screenshot or a log line.
2. **Explore.** Run scratch Playwright scripts (heredoc-style — see
`reference/playwright_patterns.md`) to discover stable selectors and
confirm filter controls exist. Use `Read` on saved PNGs to inspect UI
state. Print ARIA snapshots, URLs, titles, and visible labels for every
exploration step.
3. **Author `final_script.py`** in a fresh `final_runs/run_<id>/`. Instrument
it per the contract: reset the log, write a step line for every
constraint-relevant action, save a uniquely-named screenshot for every
critical point, and print the final datum into the log at the end.
4. **Execute** the final script once. Capture stdout/stderr.
5. **Self-verify** (this replaces `cuawright.webwright.tools.self_reflection`). Walk
`plan.md`:
- For each CP, identify a screenshot path AND/OR a log line that proves
it. `Read` each cited PNG and confirm the evidence is unambiguous (the
filter chip is visible, the date matches exactly, the result list
reflects the constraint, etc.).
- Tick the CP only when evidence is concrete. Be harsh with ambiguous,
occluded, or partially-applied states.
- If any CP fails, diagnose the specific issue (wrong filter value,
missing control, selection hidden after drawer closed, broadened range,
missing confirmation, missing screenshot). Fix `final_script.py`,
re-run inside `final_runs/run_<id+1>/`, and re-verify.
6. **Done.** Only when every CP in `plan.md` is checked off with cited
evidence. Report the final datum to the user.
## Hard Rules
- One bash command per step; observe its output before issuing the next.
- Use stable selectors and current-run evidence — never guess UI state.
- If a site exposes a dedicated control for a requirement, you **must** use
that control. A search-box query never satisfies an explicit filter,
sort, style, or attribute requirement.
- Ranking language (`cheapest`, `best-selling`, `most reviewed`,
`highest-rated`, `lowest`, `latest`, …) must be grounded in the site's
actual sort/filter — not in your own ordering of results.
- Numeric, date, quantity, and unit constraints are **exact**. Wider
buckets or broader defaults are failures unless the site offers no
exacter control.
- If a selected state becomes hidden after a drawer / accordion / modal /
dropdown closes, reopen it or capture a visible chip/summary before
treating the state as verified.
- Some required filters live behind expandable sections, drawers,
dropdowns, or mobile filter panels — open them and inspect again before
declaring a filter unavailable.
- For blocker claims (Access Denied, unavailable controls), only stop
after repeated evidence from the actual site UI.
- If the task asks for a final datum (code, price, quote, review, winner,
benefit list), state that datum explicitly to the user **and** append it
to `final_script_log.txt`.
- Do **not** install extra packages with pip/apt. `playwright`, `httpx`,
`pydantic`, etc. are already installed.
- Once `final_script.py` exists, prefer incremental edits (`Edit`) over
rewriting the whole file.
## Reference Files
- `reference/playwright_patterns.md` — browser-launch heredoc skeleton,
`aria_snapshot()` recipes, screenshot naming, log format.
- `reference/workflow.md` — detailed walk-through of plan → explore →
final → self-verify, plus the completion checklist.
- `reference/cli_tool_mode.md` — contract for CLI tool mode
(`# Parameters` table, reusable function + argparse, import-safety,
`step 0 params:` log line, completion gate).
## Slash Commands
Optional shortcuts under `commands/`:
- `/cuawright:run <task>` — default one-shot mode.
- `/cuawright:craft <task>` — CLI tool mode.
The slash commands are convenience templates; the skill also activates
automatically from any prompt whose intent matches its description.
讨论
提问、分享技巧或报告无法使用。按“有帮助”数量排序。
来自 GitHub
- GitHub 星标
- 6,097
- 开发者
- microsoft
- 许可证
- MIT
- 最近代码更新
- 2026年10月27日
- repo 中的 SKILL.md 文件(含译本和模板)
- 1