playwright-cli

name	playwright-cli
description	Authenticated browser automation for Synthex — drive real Chrome to log in, screenshot, and audit dashboard/integration surfaces. Use for live visual verification, "audit the dashboard", "check what's connected", or closing the verification gate on /dashboard/* routes. Two backends: the Playwright MCP server (interactive, in-session tools) and the committed CLI scripts (scripts/browser/*.mjs, reliable + headless). RUNS WHERE THE BROWSER + NETWORK + AUTH EXIST — i.e. a local machine, not a network-restricted sandbox.
metadata	{"author":"synthex","version":"1.0","type":"action-skill","triggers":["audit the dashboard","check what's connected","browser audit","visual verification","screenshot the dashboard","log in and check"]}
context	fork

Playwright CLI / Browser Automation

When to use

Live, authenticated checks of synthex.social surfaces: which integrations are connected, empty/error states, visual regressions — anything that needs a real logged-in browser. Pairs with browser-auth, browser-verify, site-smoke-test.

Hard reality (read first)

Browser automation runs in the environment it's launched from. A network-restricted Claude sandbox (no outbound npm, no auth session) cannot reach the authenticated app — run this on a machine with: network access, Playwright/Chromium installed, and the ability to sign in. Google SSO accounts (Continue with Google) cannot be driven headlessly; use a persistent profile + manual sign-in once, or a dedicated test account.