Playwright Skill
General-purpose Playwright automation for coding agents
Install
/plugin marketplace add lackeyjb/playwright-skillInstall command taken from the project's README or registry entry. Always review code before running it.
README excerpt
Read full README on GitHub →Playwright Skill
General-purpose Playwright automation for coding agents
An Agent Skill that enables coding agents to write and execute Playwright automation on the fly, from simple page tests to complex multi-step flows. It is also packaged as a Claude Code Plugin for convenient installation.
Claude autonomously decides when to use this skill based on your browser automation needs, loading only the minimal information required for your specific task.
Made using Claude Code.
Features
- Any Automation Task - Claude writes custom code for your specific request, not limited to pre-built scripts
- Visible Browser by Default - See automation in real-time with
headless: false - Portable executor - Runs file and inline scripts with stable module resolution
- Progressive Disclosure - Concise SKILL.md with full API reference loaded only when needed
- Safe Cleanup - Smart temp file management without race conditions
- Comprehensive Helpers - Optional utility functions for common tasks
Installation
This repository contains a standard Agent Skill and a Claude Code plugin wrapper. The recommended installation method is Vercel's skills CLI, which installs skills into the native locations for supported agents.
Why this skill?
Use this skill when the agent needs to write a real Playwright program: loops, assertions, multiple contexts, network interception, screenshots, video, or a script you want to keep and rerun. It also provides dev-server detection and a small set of focused helpers.
For straightforward interactive browsing, start with Microsoft's official
@playwright/cli and install its
agent skills with playwright-cli install --skills. For tool-based browser
control with accessibility snapshots, use
playwright-mcp. This project is
the code-first option when the automation itself is the useful artifact.
Understanding the Structure
This repository uses the plugin format with a nested structure:
playwright-skill/ # Plugin root
├── .claude-plugin/ # Plugin metadata
└── skills/
└── playwright-skill/ # The actual skill
└── SKILL.md
The repository keeps the skill inside the plugin's skills/ directory. Installers handle that layout automatically; manual copying is only a fallback for clients without an installer.
Option 1: Install with skills (Recommended)
Install globally for your user:
npx skills add lackeyjb/playwright-skill --skill playwright-skill --global --yes
Install only for the current project by omitting --global:
npx skills add lackeyjb/playwright-skill --skill playwright-skill --yes
To target specific agents, add --agent followed by one or more agent IDs:
npx skills add lackeyjb/playwright-skill --skill playwright-skill --agent claude-code cursor --global --yes
After installation, run setup from the installed skill directory:
npm run setup
See the skills CLI documentation for supported agents and options.
Option 2: Claude Code Plugin
Install via Claude Code's plugin system for automatic updates and team distribution:
Similar plugs
Makes your AI agent think like the laziest senior dev in the room. The best code is the code you never wrote.
Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Cursor, Codex, and Gemini CLI: local…
Why use many token when few token do trick. Viral skill + proxy for coding agents that cuts 65% of tokens by talking like a caveman.
Production-grade engineering skills for AI coding agents.
The 1st Collaborative AI Design Agent Workspace. Local-first and open source. Create prototypes, websites, apps, dashboards, presentations, images, and videos with your team…