Playwright CLI

Use when running Playwright via terminal CLI — `npx playwright test` (test runner), `codegen` (interactive recording), `screenshot` / `pdf` (one-off captures), and CI sharding. NOT for agent-driven real-time browser control (use `claude-in-chrome` MCP tools for that).

423 stars 6 forksTesting & QA

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add mizchi/skills --skill playwright-cli
Manual install
git clone --depth 1 https://github.com/mizchi/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/playwright-cli ~/.claude/skills/playwright-cli

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Playwright CLI

Terminal-based browser automation using `npx playwright`. This skill covers the **CLI surface**: running tests, generating test code via `codegen`, taking screenshots/PDFs, and CI sharding flags.

## Scope boundary

| I want to... | Use |
|---|---|
| Run E2E tests | `npx playwright test` (this skill) |
| Record a browser session → test code | `npx playwright codegen` (this skill) |
| One-off screenshot / PDF from a URL | `npx playwright screenshot` / `pdf` (this skill) |
| Write / review / tune a Playwright test suite | `playwright-test` skill |
| **Agent-driven real-time browser control** (navigate → click → read → assert) | `mcp__claude-in-chrome__*` tools (not this skill) |
| Interactive data scraping / SPA exploration | `claude-in-chrome` MCP tools or a Playwright script executed via `npx playwright test` |

For data scraping / SPA flows where you need to programmatically navigate, click "Load More", extract DOM, and save JSON: write a `tests/*.spec.ts` and run `npx playwright test`. See `playwright-test` skill for the test-authoring patterns.

## Quick Reference
Read the full skill on GitHub

Details

Skill name
playwright-cli
Repository
mizchi/skills
Path
playwright-cli/SKILL.md
Repo updated
18 November 2026

FAQ

What does the Playwright CLI skill do?

Use when running Playwright via terminal CLI — `npx playwright test` (test runner), `codegen` (interactive recording), `screenshot` / `pdf` (one-off captures), and CI sharding. NOT for agent-driven real-time browser control (use `claude-in-chrome` MCP tools for that).

How do I install the Playwright CLI skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add mizchi/skills --skill playwright-cli. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Playwright CLI popular?

It lives in mizchi/skills, which has 423 GitHub stars and 6 forks.

Related skills

Actions CI Tuning

423

mizchi/skills

Use when auditing or improving GitHub Actions workflows for a project. Covers cache setup (npm/pnpm/yarn), job parallelism, shard-based test splitting, artifact handling pitfalls, and Playwright-specific patterns. Trigger on: slow CI, cache miss, flaky shard jobs, merge-reports failures, or an explicit 'tune CI' request.

Testing & QA

AI Index

423

mizchi/skills

Method and tooling for measuring how AI-generated a piece of prose reads, in Japanese or English. Two layers — a deterministic lint for removable surface tells (scripts/slopscore.py, no API) and a judgment layer of typed probabilistic questions (Jev noul/score) for the tells that survive editing. Includes measured human/AI baselines, a gap-first calibration procedure, and labeled fixtures. Use when building or calibrating an AI-likeness score, or when a draft needs a defensible number rather than a vibe. For writing guidance use natural-writing-ja / natural-writing-en instead.

AI, LLMs & Agents

Apm Usage

423

mizchi/skills

Reference for APM manifests, installation, targeted updates, deployment paths and lockfiles. Invoke when the user explicitly asks about APM or apm.yml, or an unfamiliar APM command/error needs exact CLI details. Do not automatically invoke for every project that happens to have installed skills.

DevOps & Cloud

Playwright Test

423

mizchi/skills

Best practices and reference for Playwright Test (E2E). Covers how to write tests, avoiding fixed waits, network triggers, DnD, shard/retry setup on GitHub Actions, and more. Use when writing, reviewing, or configuring CI for Playwright tests.

Testing & QA

Gleam Practice

423

mizchi/skills

Use when writing or reviewing Gleam code on the Erlang target — especially Wisp + Mist HTTP services, OTP-based processes (gen_server / supervisor analogues), justfile workflows, gleeunit testing, `gleam format`, GitHub Actions CI, and performance measurement. Trigger on `gleam.toml`, `.gleam` files, or Erlang/BEAM-related symptoms even if the user does not say "Gleam" by name.

Testing & QA

Stryker Js

423

mizchi/skills

Introduce StrykerJS mutation testing or assess JavaScript/TypeScript test quality. Use Git diff mutations in CI and surviving mutants locally to find missing cases and weak assertions, including tests generated by AI.

Testing & QA

Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.