Menu
Read blocked pages or interact with them using Cloudflare Browser Run.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.
SDD-mode PR-boundary review policy for Pi. The root launches visible reviewer lanes, publishes triage, ends the turn for acknowledgement, then fixes in a separate follow-up. Review is independent of CI.
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.
Create a pull request with review, REQ backlinks, push, and CI handoff.
Verify a deployed UI in a browser for interaction, mobile layout, and visuals.
Workflow for /sdd clean — rescuing a rotted spec. Mode-aware behaviors (interactive/auto/unleashed), safety nets, what gets cleaned (incl. per-AC @impl AND @test anchor backfill at parity, gated by enforce_tdd), JUDGMENT auto-resolution rules. Invoked when /sdd clean runs. Requires the spec-driven-development skill for REQ format and Status semantics, and the spec-enforce skill family for the detection mechanics.
| name | browser-run |
| description | Read blocked pages or interact with them using Cloudflare Browser Run. |
A real headless browser (Cloudflare Browser Run, headless Chrome) for public web pages that the built-in web fetch can't read or that you need to interact with. There are two surfaces, and picking the cheaper one is the point — a real browser session is the most expensive way to touch a page.
| Surface | Tools | Cost | Use it for |
|---|---|---|---|
| Markdown / read (one-shot) | native browser_markdown, browser_content, browser_scrape | Cheap — one request, no live session | Reading a page: article/doc content, verifying rendered text/structure, pulling specific elements. The default when you just need to see what the page says. |
| Interactive | chrome-devtools via the mcp proxy (navigate_page, take_snapshot, take_screenshot, click, fill, evaluate_script, resize_page) | Expensive — opens a remote Chrome/CDP session | Driving a page: multi-step flows, clicking/typing, screenshots, viewport testing, e2e. |
Both are Pro (advanced) only, and only when a Cloudflare API token with the Browser Rendering – Edit scope is configured. If the native browser_* tools are absent, Browser Run is not enabled for this session.
web_search (pi-web-access), not Browser Run.ctx_fetch_and_index when context-mode is available; otherwise use fetch_content (pi-web-access). Plain HTTP, no JS — fast and cheap. Context-mode is optional.curl.browser_markdown (clean Markdown — smallest, best for content), browser_content (rendered HTML/DOM), or browser_scrape (specific CSS selectors). One-shot, no session — prefer this over chrome-devtools whenever you don't need to interact. Don't retry curl on a page you already know needs JS.chrome-devtools through the mcp proxy (see the pi-mcp-adapter skill for the proxy mechanics; list its tools, then call them). This is where e2e lives; see the browser-e2e skill.localhost, private IPs, or anything requiring the user's session/credentials.| Tool | Use it for |
|---|---|
browser_markdown | The default. Returns the page as clean Markdown — best for reading article/doc content. |
browser_content | Returns the fully-rendered HTML (after JS). Use when you need raw DOM/structure that Markdown drops. |
browser_scrape | Returns text + HTML + attributes for specific CSS selectors. Use to pull structured bits without ingesting the whole page. |
All three take url and an optional wait_until. For JS-heavy pages or SPAs, pass wait_until: "networkidle0" so content has rendered before capture.
browser_scrape if a page is huge.