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 Automation and agents
For makers: add a badge to your README
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/skills/microsoft-cuawright)Similar Skills
Same kind of work, ordered like the Skills list
1 skills (instruction sets) by microsoft that an AI reads and follows · not an MCP server
How a Skill differs from MCP
MCP = the hands
Connects the AI to an outside service or data, such as reading Notion or creating an invoice. A program or server has to be running.
Skill = the manual
A text file that teaches the AI how to do a task. It connects to nothing.
Some overlap: a few Skills run scripts that call tools, and a few MCP servers only send knowledge. Start from the task you want done.
Works with
Claude CodeCodex
From the maker’s README and the folders in the repo
Install
Is it safe?
- Who made it
GitHub account microsoft (organization), 12 years old
- Use and upkeep
★ 6,097 stars · code last changed Oct 27, 2026
- 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
First: which AI do you use?
Pick your app and this page shows only how to install it there
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 1Let Claude Code install it
Copy this sentence and paste it into a Claude Code 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
Restart Claude Code, then type /cuawright-web or ask for a matching task and Claude picks it up
Checked against official docs Nov 12, 2026 · Source: code.claude.com
For Terminal users
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
The maker’s recommended way
/plugin install cuawright@cuawrightCopied from the maker’s README; it downloads and runs the maker’s code
Open Terminal
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
Copy the skill folder to ~/.claude/skills
This downloads the repo to a temporary folder and copies only the folders that contain a 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-webRestart Claude Code, then type /cuawright-web or ask for a matching task and Claude picks it up
ChatGPT desktop app
The ChatGPT desktop app has Codex built in, and Codex reads skills from ~/.agents/skills
Option 1Let ChatGPT install it
Open Codex in the ChatGPT desktop app and paste this sentence into the chat
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 2Put the folder there yourself
Put the cuawright-web folder at ~/.agents/skills/cuawright-web
~ is your home folder ($HOME)
For Terminal users
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Open Terminal
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
Copy the skill folder to ~/.agents/skills
This downloads the repo to a temporary folder and copies only the folders that contain a 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
After installing
- ChatGPT desktop app: open Skills in the sidebar to see that the skill is there
- To use it: in ChatGPT type @ and pick the skill · in Codex CLI or the IDE extension run /skills or type $ and the skill name
- Codex picks up newly installed skills by itself; if one does not show up, restart Codex
Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com
ChatGPT on the web and mobile
Skills you install yourself do not work here; only skills that come with a plugin from the directory
To use this skill with ChatGPT, use the ChatGPT desktop app as above
Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com
Option 1Let Codex install it
Copy this sentence and paste it into a Codex chat · Works in Codex inside the ChatGPT desktop app, Codex CLI and the IDE extension
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 picks up newly installed skills by itself; if one does not show up, restart Codex · To use it: in ChatGPT type @ and pick the skill · in Codex CLI or the IDE extension run /skills or type $ and the skill name
Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com
For Terminal users
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Open Terminal
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
Copy the skill folder to ~/.agents/skills
This downloads the repo to a temporary folder and copies only the folders that contain a 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-webRestart Codex, then ask for a matching task; Codex lists the skill
Option 1Let Cursor install it
Copy this sentence and paste it into a Cursor 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
In Cursor’s Agent chat, type / and pick cuawright-web
Checked against official docs Nov 12, 2026 · Source: cursor.com
For Terminal users
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Open Terminal
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
Copy the skill folder to ~/.cursor/skills
This downloads the repo to a temporary folder and copies only the folders that contain a 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-webIn Cursor’s Agent chat, type / and pick cuawright-web
Option 1Let the AI install it
For other apps that read skills. The sentence gives the paths for Claude Code, Codex and Cursor so the AI picks the one for your app · 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 Nov 12, 2026 · Source: code.claude.com, learn.chatgpt.com, cursor.com
For Terminal users
Other apps that support Agent Skills (such as Gemini CLI or GitHub Copilot) use different folders. Check that app’s guide, then copy the folder with the SKILL.md there.
Skill folders checked against the official Claude Code, Codex and Cursor guides on Nov 11, 2026
✓ Commands checked Nov 16, 2026
View the original SKILL.md
The text below comes from the maker’s repo, not from PopNx MCP
7,980 characters · Open the full file on 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.
Discussion
Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
From GitHub
- GitHub stars
- 6,097
- Maker
- microsoft
- License
- MIT
- Last code change
- Oct 27, 2026
- SKILL.md files in the repo (including translated copies and templates)
- 1