← Back to Engineering & QA

Inspect a live website with a real browser

Compare browser workflows for observable UI behavior, reproduction, navigation, and evidence capture on a site you may access.

Last meaningful review July 20, 2026

The job

You need to inspect, reproduce, or document visible behavior in a running website using an interactive browser.

Includedvisible UI inspection · browser reproduction and navigation · screenshots or observable evidence

Not this pageunauthorized scraping · load testing · security assessment

30-second route

01

You need a broadly capable, standalone CLI workflow for live-site reproduction and artifacts.

It has the strongest Task fit and best SkillsMP Popular rank among direct matches, with documented navigation, snapshots, screenshots, and multi-browser support.

Editorial confidence: high
Consider Playwright Cli
02

The target requires the user's current login state or is an internal site accessible through their browser.

Its CDP workflow is expressly designed to connect to an existing Chromium browser, use its login state, work in separate background tabs, and capture screenshots.

Editorial confidence: high
Consider Web Access
03

The OpenClaw browser tool is already available and the task has multiple dependent navigation steps or likely stale refs.

It provides a concrete snapshot-first operating loop, labeled-tab hygiene, visual labels, and stale-ref recovery.

Editorial confidence: high
Consider Browser Automation
04

No compatible browser runtime, CLI, CDP connection, or OpenClaw browser tool is available.

All selected options depend on a documented browser control environment.

Editorial confidence: high
Do not claim live-browser inspection is complete.

Before you install

Install or adapt an existing Skill; do not build a new one.

The three selected Skills already provide documented, direct browser inspection, navigation, and evidence-capture workflows. Choose based on the available browser environment and session requirements.

Read the intervention guide →

Source-led comparison

What changes the choice

Facts are extracted from each selected Skill’s declared workflow. Signals describe public adoption; they are not a universal score.

Source notes

Inspect evidence and candidate limits 3 candidates

Why these candidatesEach candidate comes from tracked public sources and has a source-attributed adoption signal. This is a shortlist, not a catalogue or global ranking.

What this cannot establishWe read declared instructions and public signals. We do not run skills, benchmark outputs, audit security, or claim a universal best choice.

01

Playwright Cli

Source ↗

Use it forGeneral-purpose live-site inspection, interactive reproduction, snapshots, screenshots, and multi-browser workflows.

Avoid ifYou specifically need to take over a user's already-running, logged-in browser session.

ActionUse the CLI workflow: open or navigate, inspect a snapshot, interact through refs, capture screenshots or snapshots, then close.

EditsNone.

SetupUse an available local Playwright command through `npx playwright cli`; otherwise install `@playwright/cli` globally.

Inspect workflow and compatibility details

ContextTop public-recognition signal among direct matches (SkillsMP Popular rank 15). Its documented commands directly cover navigation, interaction, state inspection, and observable evidence.

OutputSnapshots, screenshots, PDFs, browser state, console/request output, traces, or video.

ControlCLI commands using snapshot refs, CSS selectors, or Playwright locators.

Invocationplaywright-cli

Install scopeglobal npm package if no local CLI is available

Agent fitStrong fit for repeatable, evidence-led browser inspection and reproduction.

Watch outThe source says screenshots are less common than snapshots in its normal workflow; use screenshots when visual evidence is required.

Source-visible capabilitiesNavigation and interactionOpen, navigate, click, fill, drag, select, and use tabs.explicit sourceEvidence captureSnapshots, screenshots, PDFs, traces, video, console, and requests.explicit source
CompatibilityChrome, Firefox, WebKit, and Edgedeclarednot runtime-tested
Evidence

The skill documents opening, navigating, interacting from snapshots, taking screenshots, and closing a browser.SKILL.md:lines 11-23 · inspected 2026-07-20 · high confidence

It documents screenshots/PDF output and navigation controls.SKILL.md:lines 67-103 · inspected 2026-07-20 · high confidence

It documents browser choices including Chrome, Firefox, WebKit, and Edge, plus attachment to running Chrome or Edge.SKILL.md:lines 210-247 · inspected 2026-07-20 · high confidence

It documents local and global CLI availability paths.SKILL.md:lines 343-355 · inspected 2026-07-20 · high confidence

Public signal15 /SkillsMP source-specifictop-rankinteractive-browserevidence-capturemulti-browserexplicit source
02

Web Access

Source ↗

Use it forInspecting a site through the user's existing Chrome/Edge login state, including internal or login-gated pages, with screenshots and DOM-driven navigation.

Avoid ifAn isolated browser session is sufficient, or setup cannot meet its Node.js 22+ and CDP prerequisites.

ActionRun the dependency check, create a background tab through the CDP proxy, inspect with `/eval`, navigate/click/scroll as needed, capture a screenshot, and close only the created tab.

EditsNone.

SetupRequires Node.js 22+ and a working CDP connection/proxy to a Chromium browser; the source directs a dependency check before use.

Inspect workflow and compatibility details

ContextSecond-highest SkillsMP Popular rank (26) among direct matches. It is particularly useful where live inspection requires an existing authenticated browser session.

OutputPage information, DOM-derived observations, rendered screenshots, and interaction results.

ControlHTTP API over a CDP proxy connected to the user's daily browser.

Invocationnode "${CLAUDE_SKILL_DIR}/scripts/check-deps.mjs" followed by curl calls to the CDP proxy

Install scoperuntime prerequisite: Node.js 22+ plus Chrome/Edge/Chromium CDP availability

Agent fitStrong fit for session-aware inspection; explicitly preserves existing user tabs while using its own background tab.

Watch outIts instructions require displaying an automation-account-risk notice before CDP operation; it also warns that dense tab creation can trigger anti-bot controls.

Source-visible capabilitiesAuthenticated live-browser accessConnects through CDP to a user's Chromium browser and its login state.explicit sourceInspection and evidenceDOM evaluation, navigation, clicks, scrolling, and rendered screenshots.explicit source
CompatibilityChrome, Edge, and Chromium-family browsersdeclarednot runtime-tested
Public signal26 /SkillsMP source-specificlogged-in-sessionreal-browsercdpevidence-captureexplicit source
03

Browser Automation

Source ↗

Use it forMulti-step browser inspection with disciplined tab management, snapshot-first interaction, visual labels, and explicit recovery from stale references.

Avoid ifThe required OpenClaw browser tool is unavailable, or you need a standalone CLI rather than an OpenClaw-specific browser workflow.

ActionCheck browser state and tabs, open or reuse a labeled tab, take an ARIA snapshot, act through fresh refs, capture labeled visual evidence when needed, and report any manual blocker.

EditsNone.

SetupRequires the OpenClaw `browser` tool; use its status/doctor checks when browser or plugin setup may be broken.

Inspect workflow and compatibility details

ContextThird-best direct match by SkillsMP Popular rank (68). Its workflow is narrower than the first two but clearly supports live navigation, visible inspection, and evidence-oriented interaction.

OutputARIA snapshots, labeled screenshots, stable tab handles, and explicit blocker reports.

ControlOpenClaw browser-tool actions with labeled tabs and stable target IDs.

Invocationopenclaw browser doctor or browser tool actions

Install scopeOpenClaw browser tool environment

Agent fitStrong fit when the OpenClaw browser environment is already available and the inspection has several dependent steps.

Watch outLabeled screenshots have documented limitations on existing-session profiles and are unavailable in the raw-CDP fallback.

Source-visible capabilitiesStable multi-step navigationChecks browser state, uses labels and stable tab handles, and reuses tabs.explicit sourceVisible inspection and recoveryUses snapshots before interaction, supports labeled visual context, and defines stale-ref recovery.explicit source
CompatibilityOpenClaw browser tooldeclarednot runtime-tested
Public signal68 /SkillsMP source-specificsnapshot-firsttab-hygienestale-ref-recoveryobservable-uiexplicit source

Still comparing?

Tell us the job, not just the skill names.

Request a task guide
Did this decision map help?