Playwright Automation Agent Skill
Browser automation and testing with Playwright. Use when testing web applications, automating browser tasks, taking screenshots, or validating UI behavior.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/majiayu000/spellbook --skill playwright-automationThe instruction itself
4 sections, as written by the authorPlaywright Browser Automation
Use this skill for Playwright scripts that inspect pages, capture screenshots, automate forms, test responsive views, or collect console/network evidence.
Routing
- Start here to confirm scope, safety boundaries, and the minimum workflow.
- Load
references/full-guide.mdbefore executing detailed commands, applying templates, or relying on examples from this skill. - Keep the work limited to the user-requested target; do not add adjacent improvements unless the user asks.
Quick Workflow
- Confirm the target, available context, constraints, and done-when signal.
- Read the relevant section of
references/full-guide.mdfor task-specific details. - Execute the smallest reversible action that satisfies the request.
- Verify with a runnable script, explicit target URL, captured output or artifact path, and cleanup of any started local servers.
- Report changed files, commands run, evidence collected, and any remaining risk.
References
references/full-guide.md- complete command patterns, examples, checklists, and edge cases.
Other skills for the same job
different authors, same section of the catalogue
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
Use this skill to query your Google NotebookLM notebooks directly from Claude Code for source-grounded, citation-backed answers from Gemini. Browser automation, library management, persistent auth. Drastically reduced hallucinations through document-only responses.
Complete browser automation with Playwright. Auto-detects dev servers, writes clean test scripts to /tmp. Test pages, fill forms, take screenshots, check responsive design, validate UX, test login flows, check links, automate any browser task. Use when user wants to test websites, automate browser interactions, validate web functionality, or perform any browser-based testing.
Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include "automate Slack app", "control VS Code", "interact with Discord app", "test this Electron app", "connect to desktop app", or any task requiring automation of a native Electron application.
Use when the task requires automating a real browser from the terminal (navigation, form filling, snapshots, screenshots, data extraction, UI-flow debugging) via `playwright-cli` or the bundled wrapper script.
Use when the user explicitly asks for a desktop or system screenshot (full screen, specific app or window, or a pixel region), or when tool-specific capture capabilities are unavailable and an OS-level capture is needed.
| 所有联网操作必须通过此 skill 处理，包括：搜索、网页抓取、登录后操作、动态页面交互等。 触发场景：用户要求搜索信息、查看网页内容、访问需要登录的网站、操作网页界面、抓取社交媒体内容（小红书、微博、推特等）、读取动态渲染页面、以及任何需要真实浏览器环境的网络任务。
Automate Anchor Browser tasks via Rube MCP (Composio). Always search tools first for current schemas.
How to use it
Take majiayu000/playwright-automation from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.