by lackeyjb
Claude Code Skill for browser automation with Playwright. Model-invoked - Claude autonomously writes and executes custom automation for testing and validation.
# Add to your Claude Code skills
git clone https://github.com/lackeyjb/playwright-skillGuides for using testing skills like playwright-skill.
Last scanned: 4/23/2026
{
"issues": [],
"status": "PASSED",
"scannedAt": "2026-04-23T06:08:08.873Z",
"semgrepRan": false,
"npmAuditRan": true,
"pipAuditRan": true
}playwright-skill is an open-source testing skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by lackeyjb. Claude Code Skill for browser automation with Playwright. Model-invoked - Claude autonomously writes and executes custom automation for testing and validation. It has 2,888 GitHub stars.
Yes. playwright-skill passed SkillsLLM's automated security scan — a dependency vulnerability audit plus prompt-injection heuristics — with no high-severity issues. You can read the full report in the Security Report section on this page.
Clone the repository with "git clone https://github.com/lackeyjb/playwright-skill" and add it to your Claude Code skills directory (see the Installation section above).
playwright-skill is primarily written in JavaScript. It is open-source under lackeyjb on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other Testing skills you can browse and compare side by side. Open the Testing category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh playwright-skill against similar tools.
No comments yet. Be the first to share your thoughts!
Top skills in this category by stars
Based on votes and bookmarks from developers who liked this skill
General-purpose browser automation as a Claude Skill
A Claude Skill that enables Claude to write and execute any Playwright automation on-the-fly - from simple page tests to complex multi-step flows. Packaged as a Claude Code Plugin for easy installation and distribution.
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.
headless: falseThis repository is structured as a Claude Code Plugin containing a skill. You can install it as either a plugin (recommended) or extract it as a standalone skill.
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
Claude Code expects skills to be directly in folders under .claude/skills/, so manual installation requires extracting the nested skill folder.
Install via Claude Code's plugin system for automatic updates and team distribution:
# Add this repository as a marketplace
/plugin marketplace add lackeyjb/playwright-skill
# Install the plugin
/plugin install playwright-skill@playwright-skill
# Navigate to the skill directory and run setup
cd ~/.claude/plugins/marketplaces/playwright-skill/skills/playwright-skill
npm run setup
Verify installation by running /help to confirm the skill is available.
To install as a standalone skill (without the plugin system), extract only the skill folder:
Global Installation (Available Everywhere):
# Clone to a temporary location
git clone https://github.com/lackeyjb/playwright-skill.git /tmp/playwright-skill-temp
# Copy only the skill folder to your global skills directory
mkdir -p ~/.claude/skills
cp -r /tmp/playwright-skill-temp/skills/playwright-skill ~/.claude/skills/
# Navigate to the skill and run setup
cd ~/.claude/skills/playwright-skill
npm run setup
# Clean up temporary files
rm -rf /tmp/playwright-skill-temp
Project-Specific Installation:
# Clone to a temporary location
git clone https://github.com/lackeyjb/playwright-skill.git /tmp/playwright-skill-temp
# Copy only the skill folder to your project
mkdir -p .claude/skills
cp -r /tmp/playwright-skill-temp/skills/playwright-skill .claude/skills/
# Navigate to the skill and run setup
cd .claude/skills/playwright-skill
npm run setup
# Clean up temporary files
rm -rf /tmp/playwright-skill-temp
Why this structure? The plugin format requires the skills/ directory for organizing multiple skills within a plugin. When installing as a standalone skill, you only need the inner skills/playwright-skill/ folder contents.
skills/playwright-skill/ folder to:
~/.claude/skills/playwright-skill/path/to/your/project/.claude/skills/playwright-skillcd ~/.claude/skills/playwright-skill # or your project path
npm run setup
Run /help to confirm the skill is loaded, then ask Claude to perform a simple browser task like "Test if google.com loads".
After installation, simply ask Claude to test or automate any browser task. Claude will write custom Playwright code, execute it, and return results with screenshots and console output.
"Test the homepage"
"Check if the contact form works"
"Verify the signup flow"
"Take screenshots of the dashboard in mobile and desktop"
"Test responsive design across different viewports"
"Fill out the registration form and submit it"
"Click through the main navigation"
"Test the search functionality"
"Check for broken links"
"Verify all images load"
"Test form validation"
Default settings:
false (browser visible unless explicitly requested otherwise)100ms for visibility30s/tmp/playwright-skill/
├── .claude-plugin/
│ ├── plugin.json # Plugin metadata for distribution
│ └── marketplace.json # Marketplace configuration
├── skills/
│ └── playwright-skill/ # The actual skill (Claude discovers this)
│ ├── SKILL.md # What Claude reads
│ ├── run.js # Universal executor (proper module resolution)
│ ├── package.json # Dependencies & setup scripts
│ └── lib/
│ └── helpers.js # Optional utility functions
│ └── API_REFERENCE.md # Full Playwright API reference
├── README.md # This file - user documentation
├── CONTRIBUTING.md # Contribution guidelines
└── LICENSE # MIT License
Claude will automatically load API_REFERENCE.md when needed for comprehensive documentation on selectors, network interception, authentication, visual regression testing, mobile emulation, performance testing, and debugging.
npm run setup)npm run setup)Playwright not installed?
Navigate to the skill directory and run npm run setup.
Module not found errors?
Ensure automation runs via run.js, which handles module resolution.
Browser doesn't open?
Verify headless: false is set. The skill defaults to visible browser unless headless mode is requested.
Install all browsers?
Run npm run install-all-browsers from the skill directory.
Agent Skills are folders of instructions, scripts, and resources that agents can discover and use to do things more accurately and efficiently. When you ask Claude to test a webpage or automate browser interactions, Claude discovers this skill, loads the necessary instructions, executes custom Playwright code, and returns results with screenshots and console output.
This Playwright skill implements the open Agent Skills specification, making it compatible across agent platforms.
Contributions are welcome. Fork the repository, create a feature branch, make your changes, and submit a pull request. See CONTRIBUTING.md for details.
MIT License - see LICENSE file for details.