playwright: Skill for Claude Code

.claude/skills/playwright-test-results/SKILL.md

playwright-test-results is a skill for Claude Code from microsoft/playwright. It costs 45 tokens per session (2,292 once invoked), scanned A, original, Apache-2.0.

A skill for querying a DuckDB database containing recent Playwright continuous-integration test results. Continuous integration, or CI, automatically builds and tests code after changes are made.

In plain words
What is it for?
Use it to query failed tests, flaky tests, slow tests, and results grouped by test run, commit, or pull request.
Why use it?
It avoids searching through separate CI runs and stored test artifacts to find failure, flakiness, speed, or pull-request information.

Skill for Claude Code ✓ vendor

Written for Claude Code: user-invocable in frontmatter.

This is microsoft/playwright's own configuration. It tells Claude Code how to work on playwright itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything playwright configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is GITHUB_TOKEN=$(gh auth token) node utils/test-results-db/cli.ts update --lookback-days 3.

About the project

Playwright is a framework for automating and testing websites through one API that drives Chromium, Firefox, and WebKit. Developers use it for end-to-end tests, browser automation scripts, and AI-agent web interactions. The catalogue add-ons help coding and AI agents use Playwright for testing and browser automation.

microsoft/playwright · 98,318 stars · on GitHub · playwright.dev

Reuse

Borrowing it

Nothing to install: this file belongs to microsoft/playwright. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/microsoft/playwright/main/.claude/skills/playwright-test-results/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/microsoft/playwright

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for playwright-test-results

README.md
[![agentmods](https://agentmods.dev/badge/skills/microsoft/playwright/playwright-test-results/github.svg)](https://agentmods.dev/skills/microsoft/playwright/playwright-test-results)
Your own site
<a href="https://agentmods.dev/skills/microsoft/playwright/playwright-test-results"><img src="https://agentmods.dev/badge/skills/microsoft/playwright/playwright-test-results/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for playwright-test-results

Your own site · 80×15
<a href="https://agentmods.dev/skills/microsoft/playwright/playwright-test-results"><img src="https://agentmods.dev/badge/skills/microsoft/playwright/playwright-test-results.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 45 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,292 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • Snyk pass 6 Sept 2026
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00045 $0.02292
Opus 5.5 $0.00018 $0.00917
Sonnet 5.5 $0.00009 $0.00458
Haiku 4.5 $0.00005 $0.00229

Measured 3d ago against content hash 57d4691c6bdb, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

playwright-test-results scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/playwright-test-results/SKILL.md · 211 lines

How it starts

The opening of the file, as written. The whole thing — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Playwright Test Results (DuckDB)

A single DuckDB file holds recent Playwright CI test results, so you can answer questions about failures, flakiness, and slow tests with plain SQL. It is refreshed every few hours.

Get the database

Download the latest snapshot and top it up with the newest runs:

npm ci                       # first time only, from the repo root
GITHUB_TOKEN=$(gh auth token) node utils/test-results-db/cli.ts update --lookback-days 3

update downloads the snapshot first when there is no local database, then ingests only the artifacts the snapshot lacks. Never delete the database to rebuild it: every artifact costs one GitHub API request, the budget is shared by every workflow in the repository, and a rebuild of a few days exhausts it. To only refresh the snapshot without ingesting, run download.

Query it through the bundled @duckdb/node-api binding — no separate DuckDB install needed, it ships in node_modules after npm ci:

node --input-type=module -e '
import { DuckDBInstance } from "@duckdb/node-api";
const conn = await (await DuckDBInstance.create("utils/test-results-db/test-results.duckdb")).connect();
console.table((await conn.runAndReadAll(process.argv[1])).getRowObjectsJson());
' "SELECT count(*) FROM test_results"

Integer columns come back as strings (JSON-safe), so do ranking and filtering in SQL, not in JS.

Schema

Single table test_results, one row per test result (one row per retry). The columns are inferred from the parquet the reporter emits (tests/config/parquetReporter.ts), plus two trailing columns this CLI adds:

Column Meaning
run_id, run_attempt GitHub Actions run identity
run_started_at when the run started
workflow_name e.g. tests 1 / tests 2 / tests others / MCP
event push / pull_request
head_sha, head_branch, pr_number what was tested
bot_name e.g. chromium-ubuntu-22.04-node20, webkit-macos-15-large — the CI bot. OS and arch are encoded here; there is no separate os column.
project_name CI project = browser + suite, e.g. chromium-page, webkit-library, playwright-test
test_title title path within the file, joined by › (describe › test)
file, line, column_number source location (file is relative to repo root)
expected_status passed / skipped / ...
status actual result: passed / failed / timedOut / skipped / interrupted
retry 0 = first attempt
result_started_at when this attempt started
duration_ms result duration
error_message all errors joined, ANSI-stripped (NULL when none)
tags list of strings, e.g. ['@slow', '@flaky'] (use list functions / list_contains)
annotations list of {type, description} structs, e.g. [{'type': 'skip', 'description': 'flaky on CI'}] (empty list when none)
artifact_id the GitHub artifact this row came from (dedupe key)
ingested_at debug only — when this row was imported

Read the full file on GitHub · 211 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 3d ago Changed 57d4691c6bdb
  2. 1mo ago First seen · 211 lines · 45 tokens per session scan A 3fd24911309f

Subscribe to this mod's changes

playwright-test-results is a skill published in the GitHub repository microsoft/playwright (98,318 stars, last pushed today), licensed Apache-2.0. It adds 45 tokens to every session and 2,292 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

reproduce-bug

Reproduce a reported bug in googleapis/mcp-toolbox and decide whether it is real, delivering an evidence-backed verdict: confirmed, already fixed, misconfiguration, client-side, works as intended, not reproducible, or blocked. Use whenever a maintainer asks you to reproduce, verify, confirm, or investigate a bug…

googleapis/mcp-toolbox · 130 tokens

compatibility-testing

Cross-browser, cross-platform, and cross-device compatibility testing ensuring consistent experience across environments. Use when validating browser support, testing responsive design, or ensuring platform compatibility.

proffesor-for-testing/agentic-qe · 36 tokens

Axe-core Accessibility Testing

Accessibility testing skill using axe-core and Playwright for automated WCAG 2.1 compliance auditing, custom rules, and accessibility reporting.

PramodDutta/qaskills · 33 tokens

e2e-testing

Use when writing or stabilizing Playwright tests that drive a real browser through multi-step journeys — durable locators, web-first assertions, storageState auth, trace/retries, and flakes that only bite in CI. NOT in-process component tests (that is testing-web), NOT WCAG auditing (that is accessibility), NOT the…

ericrisco/rsc-harness · 79 tokens

Flaky Test Doctor

Diagnose flaky test failures from Playwright reports, traces, and rerun history. Classify each failure as product, test, environment, data, or unknown with cited evidence and a proposed fix. Never auto-modifies code without opt-in.

PramodDutta/qaskills · 54 tokens

Checkly Monitoring as Code

Teach agents to build synthetic monitoring as code with Checkly, including Playwright browser checks, API checks, alerting, and CI deploy workflows.

PramodDutta/qaskills · 35 tokens