playwright-cli
The playwright-cli skill provides a command-line interface for automating browser interactions, testing web pages, and managing browser sessions using Playwright.
Is playwright-cli safe to install?
Review the source first: our audit of playwright-cli's source files found 3 shell commands, 1 external URL, file reads and writes (high risk). Every command and URL listed appears verbatim in the skill's source. The skill executes shell commands, interacts with local files for uploads and storage, and can connect to external browser CDP endpoints.
How we audit skills: our security review methodology.
Who is this skill for?
Developers and testers who need to automate browser tasks, perform web testing, or debug web applications via a command-line interface.
What can you do with it?
- Automating form submissions and multi-tab workflows
- Capturing screenshots, PDFs, and browser snapshots
- Managing browser cookies, local storage, and session storage
- Mocking network requests
- Debugging web pages using console logs and request inspection
- Recording browser sessions and generating Playwright locators
- Performing UI reviews through interactive annotations
How good is this skill?
Quality score: 10/10. The documentation is comprehensive, providing clear command examples, usage patterns, and installation instructions.
What does the skill file contain?
# Browser Automation with playwright-cli ## Quick start ```bash # open new browser playwright-cli open # navigate to a page playwright-cli goto https://playwright.dev # interact with the page using refs from the snapshot playwright-cli click e15 playwright-cli type "page.click" playwright-cli press Enter # take a screenshot (rarely used, as snapshot is more common) playwright-cli screenshot # close the browser playwright-cli close ``` ## Commands ### Core ```bash playwright-cli open # open and navigate right away playwright-cli open https://example.com/ playwright-cli goto https://playwri...
Frequently asked questions
How do I interact with elements on a page?
Use the refs provided in the browser snapshot (e.g., e15) or use CSS selectors and Playwright locators directly in commands.
Can I persist browser sessions?
Yes, use the --persistent flag when opening a browser or save/load state using the state-save and state-load commands.
How do I capture output for use in other tools?
Use the --raw flag to strip metadata and return only the result value, which can be piped to other utilities like jq.
What browsers are supported?
The CLI supports chrome, firefox, webkit, and msedge.
Related skills
find-skills
2.3MUsers seeking to extend agent capabilities with specialized tools, workflows, or knowledge packages
The find-skills skill enables agents to search for, discover, and install modular packages from the open agent skills ecosystem using the Skills CLI.
agent-browser
506.7KAI agents and developers requiring programmatic web interaction, exploratory testing, or automation of Electron desktop applications
The agent-browser CLI provides browser automation for AI agents using Chrome or Chromium via CDP. It supports page navigation, form interaction, data extraction, and testing. The tool utilizes accessibility-tree snapshots and element references for interaction.
video-edit
338.7KUsers of the RunComfy CLI who need to automate video editing tasks like restyling, background swapping, or motion transfer
The video-edit skill acts as a router for the RunComfy CLI, selecting between Wan 2.7 Edit-Video, Kling 2.6 Pro Motion Control, and Lucy Edit Restyle models based on user intent to perform video transformations.
agentspace
324.0KDevelopers and AI agent users who need to share, monitor, or collaborate on agent-generated files and workspaces in real-time
Agentspace provides a mechanism to share local agent files, logs, and artifacts via a live browser-accessible URL. It enables remote viewing, commenting, and editing of specified local paths through the ascli command-line tool.