playwright-cli
Skill30 starsChanged 9 days agoMITView on GitHub
Browser automation via the Playwright CLI for validating PMX Canvas, embedded web artifacts, and external integrations from the terminal. Use when you need to open pages, click through UI flows, inspect element structure, take screenshots, or verify that a canvas-hosted app actually works in the browser.
- Installs packages
180 other projects use a version of this.
Adopted by
Most recently taken up by
- idavidov13/agentic-playwrighttheir own version, first seen Nov 8, 2026
- kurofune/claudittheir own version, first seen Nov 8, 2026
- naman10parikh/pennytheir own version, first seen Nov 8, 2026
- n1kben/agentstheir own version, first seen Nov 8, 2026
- Today-Weekly-Release-Company/codex-inittheir own version, first seen Nov 8, 2026
- taixuann/development-spacetheir own version, first seen Nov 8, 2026
Used with
Projects with it also use fabric-sdk, ecosystem-reference and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
MicrosoftSkillfabric-sdk
How to use @microsoft/fabric-app-data to connect web applications to Fabric data sources at runtime. Build browser-based apps that query semantic models via DAX using the FabricClient API.
Also in 9 projects that use this
naman10parikhSkillecosystem-reference
Quick-access directory of Claude Code ecosystem repos, skills, plugins, MCPs, and patterns. Use when improving the harness.
Also in 5 projects that use this
naman10parikhSkillfractal-delegation
Also in 5 projects that use this
MicrosoftSkillschema-discovery
Explore Power BI semantic model schemas using DAX INFO functions. Progressive metadata discovery strategy, scope estimation, and narrowing techniques for tables, columns, measures, and relationships.
Also in 9 projects that use this
- +6 more from naman10parikh
- +2 more from microsoft
Other versions180 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 180
- microsoft/playwright★ 100ksame name
- coleam00/Archon★ 24ksame name
- microsoft/playwright-cli★ 15ksame name
- dotnet/eShop★ 11ksame name
- TypeCellOS/BlockNote★ 10ksame name
- sanity-io/sanity★ 6.4ksame name
- github/gh-aw★ 5.6ksame name
- zebbern/claude-code-guide★ 4.7ksame name
- pwndoc/pwndoc★ 2.9ksame name
- jdecked/twemoji★ 1.9ksame name
170 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository20 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- control-session-orchestratorSkill
- data-analysisSkill
- doc-coauthoringSkill
- frontend-designSkill
- json-render-codegenSkill
- json-render-coreSkill
- json-render-inkSkill
- json-render-mcpSkill
- json-render-reactSkill
- json-render-shadcnSkill
- pmx-canvas-orchestrationSkill
- pmx-canvasSkill
- pmx-canvas-testingSkill
- published-consumer-e2eSkill
- tufte-vizSkill
- web-artifacts-builderSkill
- web-design-guidelinesSkill
The file
We split this skill into the rules it gives an agent
10 rules. 0 are common, 6 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 161 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this skill when PMX Canvas work needs a real browser check instead of static inspection.
- Distinctive: line 12
Verify a PMX Canvas UI flow after changing the client
- Distinctive: line 30
Read the saved snapshot file to find element refs
- Distinctive: line 32
Verify with another snapshot or a screenshot
- Very specific: line 58
Start the canvas first: bun run src/cli/index.ts --no-open
- Very specific: line 59
Use this skill after canvas_app { action: "build-artifact" } when you need browser validation
- Distinctive: line 60
Prefer visible browser automation for UI investigation so the human can follow along
- Very specific: line 65
Use pmx-canvas to create, pin, connect, and inspect nodes
- Very specific: line 66
Use web-artifacts-builder to scaffold richer React/shadcn artifacts
- Distinctive: line 67
Use this skill to validate the generated artifact route and embedded canvas node in a browser
“Common” is measured: kept by at least 6 in 10 of the 161 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Playwright CLI
Use this skill when PMX Canvas work needs a real browser check instead of static inspection.
When To Use
- Verify a PMX Canvas UI flow after changing the client
- Open an embedded
mcp-appor/artifact?path=...route and confirm it renders - Click through context menus, pins, groups, snapshots, and other browser-only interactions
- Capture screenshots or accessibility snapshots while keeping terminal context small
Prerequisites
npm install -g @playwright/cli@latest
playwright-cli --versionRequires Node.js 18+.
Core Workflow
- Open the target URL with
playwright-cli open <url> - Capture a structural snapshot with
playwright-cli snapshot - Read the saved snapshot file to find element refs
- Interact with the page using
click,fill,press, orgoto - Verify with another snapshot or a screenshot
- Close the session when done
For PMX Canvas work, prefer a named session so you can keep a browser attached to the canvas while testing artifact tabs separately.
playwright-cli -s=canvas open http://localhost:4313
playwright-cli -s=canvas snapshot
playwright-cli -s=canvas screenshot
playwright-cli -s=canvas closeCommands You Will Use Most
open [url]— launch browser and optionally navigategoto <url>— move to another pagesnapshot— save page structure to diskscreenshot [ref]— capture page or element imageclick <ref>— click an element by snapshot reffill <ref> <text>— fill an input or textareapress <key>— send keyboard inputtab-new [url],tab-list,tab-select <index>— manage multiple pagesclose— close the current browser session
PMX Canvas Guidance
- Start the canvas first:
bun run src/cli/index.ts --no-open - Use this skill after
canvas_app { action: "build-artifact" }when you need browser validation - Prefer visible browser automation for UI investigation so the human can follow along
- Store screenshots and snapshots on disk, then only read back the specific files you need
Pairing With Other Skills
- Use
pmx-canvasto create, pin, connect, and inspect nodes - Use
web-artifacts-builderto scaffold richer React/shadcn artifacts - Use this skill to validate the generated artifact route and embedded canvas node in a browser
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

