Labsco
Labsco/Repos/microsoft/playwright
REPO PACKAGE

microsoft playwright

OFFICIAL
microsoft · publisher92,271 repository starsApache-2.0 · Freegithub.com/microsoft/playwright
5skills
1ready to use

playwright-cli automates browser interactions and runs Playwright tests, and works for anyone using Playwright. playwright-trace reads a Playwright trace file from the command line — actions, requests, console output, errors, snapshots — which is useful to any test author debugging a failure, not just the Playwright team.

The other four are the Playwright team's own maintainer tooling. playwright-dev explains how to extend Playwright itself — adding APIs, MCP tools, or CLI commands. playwright-devops handles CI failure analysis, workflow debugging, and releases for the microsoft/playwright repo specifically. playwright-triage reproduces a bug from a GitHub issue's description. playwright-bot-voice is the house style guide for anything the Playwright bot posts publicly under its own name — issue comments, PR descriptions, release notes — so agent-written text reads as one maintainer's voice rather than a model's.

READ THE FULL ANALYSIS

This is a much narrower slice than the Playwright README describes. The README covers Playwright Test, the Playwright CLI package, Playwright MCP, the Playwright Library, and a VS Code extension — five separate ways to use Playwright. The six skills in this repo don't teach any of that directly; they are a bug-triage and repo-maintenance layer sitting on top, written for people who work on Playwright's own codebase.

playwright-devops needs GitHub access it doesn't advertise up front. Downloading failed CI job logs requires reachable GitHub Actions credentials — fine inside Microsoft's own CI, not something an outside reader can just run.

Checked 19 September 2026 against the live skill set and the repository README.

1Work with nothing else to set up.
92,271Stars on the GitHub repository, at last check.