Skip to content
Get packs

Guide · Agent skill

How to use the Playwright Test Reporter agent skill

Updated · written with AI from the project's own documentation and checked against our catalogue data

The Playwright Test Reporter is an agent skill that tells an AI coding agent how to turn your Playwright end-to-end browser test results into a readable status report. It is written for developers and QA engineers who already use Playwright and want a quick summary instead of raw test output. By the end of this guide you will know what the skill does, how to install it, how to trigger it with a plain request, and what to check before running it.

Playwright Test Reporteralirezarezvani/claude-skills · MIT

Quick start

  1. 1Download the ZIP. Download the skill ZIP from this page. It contains the SKILL.md file for the report skill.
  2. 2Unzip into a skills folder. Unzip it into ~/.claude/skills/ for personal use, or into .claude/skills/ in a project.
  3. 3Confirm your Playwright project. Make sure Node.js and npx are installed and that your working directory contains a Playwright test project.
  4. 4Set optional variables. If you want Slack posts or TestRail pushes, set SLACK_WEBHOOK_URL or TESTRAIL_URL in your environment.
  5. 5Ask for a report. Say something like "test report" or "how did tests go" in your agent session.
  6. 6Review the output. Read the summary, check the failing tests and error messages, and open the markdown file in test-reports/.

What is an agent skill?

An agent skill is a folder containing a SKILL.md file with instructions that an AI agent can load when a request matches the skill's description. The agent reads those instructions and follows them, using the tools already available to it.

This skill's folder is engineering-team/playwright-pro/skills/report in the alirezarezvani/claude-skills repository, and its only listed file is SKILL.md. It is released under the MIT licence.

What the skill makes the agent do

When you ask for a test report, the agent first checks for recent results in test-results/ and playwright-report/. If none exist, it runs your Playwright tests. It then reads the total, passed, failed, skipped and flaky counts, along with duration per test and overall, and lists failing tests with their error messages.

The agent saves a markdown report to test-reports/ using a date-stamped filename. It also checks which destinations are configured and routes results to them. If it finds a Slack webhook, it posts a summary. If it finds TestRail settings, it pushes results. If it sees an HTML report folder, it opens or serves the report. When earlier reports exist, it compares pass rates and highlights new and recurring failures.

  • Summary of pass, fail, skip and flaky counts
  • Failed test names with error messages and file locations
  • Flaky tests (those that passed on retry)
  • A by-browser breakdown (Chromium, Firefox, WebKit)
  • Trend comparison when historical reports exist

Install the skill

You can install the skill in two ways. Download the ZIP from the skill's page on this directory and unzip it into your personal skills folder at ~/.claude/skills/, or into a project's .claude/skills/ folder if you want it limited to one repository.

Alternatively, in the Claude apps, open Settings, go to Capabilities, and upload the skill under Skills.

  • Personal install: unzip into ~/.claude/skills/
  • Project install: unzip into .claude/skills/ inside your project
  • Claude apps: Settings → Capabilities → Skills, then upload

Check what you need before you start

The skill assumes a working Playwright setup. Node.js and npx must be available, and the working directory must contain a Playwright test project. The steps call npx playwright test directly, so the skill will not produce useful results without it.

Slack and TestRail are optional. Slack posting needs the SLACK_WEBHOOK_URL environment variable. TestRail pushing needs the TESTRAIL_URL environment variable and the /pw:testrail command.

  • Node.js and npx
  • A Playwright test project in the working directory
  • Optional: SLACK_WEBHOOK_URL for Slack posts
  • Optional: TESTRAIL_URL and the /pw:testrail command for TestRail pushes

Trigger the skill with a natural request

You do not need to name the skill. The description lists phrases that should activate it. Ask in plain language, for example: test report, results summary, test status, show results, test dashboard, or how did tests go.

The agent will reuse recent results if they exist, so ask for a fresh run if you have changed code since the last one.

  • "Give me a test report"
  • "How did tests go?"
  • "Show results for the checkout tests"
  • "What's the test status on this branch?"

Safety notes: scripts and network access

This skill runs scripts and uses the network. It executes your test commands, and if the matching environment variables are set, it sends summaries to Slack or results to TestRail. Those posts go to shared team channels.

Do not run it against production or shared environments without checking first. Confirm your environment variables point where you expect before asking for a report.

  • It executes test commands in your project.
  • It may post to a Slack channel if SLACK_WEBHOOK_URL is set.
  • It may push results to TestRail if TESTRAIL_URL is set.
  • Check target environments before running tests against anything shared or live.

What people use it for

  • A developer asks how the test run went and gets counts plus failing test names without scrolling raw output.
  • A QA engineer has results posted to a Slack channel after each run when SLACK_WEBHOOK_URL is configured.
  • A team keeps a dated folder of markdown reports in test-reports/ to see which tests became flaky over time.
  • A CI-minded team uses the HTML report location detection to find playwright-report/index.html.

Frequently asked questions

How do I install the Playwright Test Reporter skill?

Download the ZIP from this page and unzip it into ~/.claude/skills/ for personal use or .claude/skills/ inside a project. You can also upload it in the Claude apps under Settings → Capabilities → Skills.

What does the report skill require?

It requires Node.js and npx, plus a Playwright test project in your working directory. Slack posting needs SLACK_WEBHOOK_URL, and TestRail pushing needs TESTRAIL_URL and the /pw:testrail command.

Is the Playwright Test Reporter skill free?

The skill is released under the MIT licence, as stated on its listing. Check the repository licence file for the full terms.

Does it work with projects that don't use Playwright?

No. The steps are built around Playwright commands and reporters, so the skill will not produce useful results in other projects.

Will it post to Slack or TestRail automatically?

Only if the matching settings exist. The skill checks for SLACK_WEBHOOK_URL and TESTRAIL_URL and routes results to whichever is configured, otherwise it generates a markdown report.

Why does the skill run my tests again?

If it finds no recent results in test-results/ or playwright-report/, it runs npx playwright test. Ask for a fresh run after code changes so the report reflects current code.

New agent skills, repos and AI tools — every week

The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.

Our verdict

Use this skill if you already run Playwright and want a fast, saved summary of results, with optional Slack or TestRail posting. Pick something else if your project does not use Playwright, or if you need to run tests against shared or production environments without extra checks.

Download the skill