playwright-triage Skill
Triage a Playwright bug report by reproducing it from the information in the issue. Use when asked to triage, reproduce, or verify a GitHub issue (a new bug report, or an existing report with a new comment). Published by microsoft in playwright.
What is playwright-triage Skill?
Triage a Playwright bug report by reproducing it from the information in the issue. Use when asked to triage, reproduce, or verify a GitHub issue (a new bug report, or an existing report with a new comment). Published by microsoft in playwright. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Browser automation
- Testing
- Documentation
- Design and media
- Research
Technical details
- Install or run with Copy skill directory
When to use playwright-triage Skill
- Use it for browser automation.
- Use it for testing.
- Use it for documentation.
- Use it for design and media.
- Use it for research.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/playwright
- Skill file: .claude/skills/playwright-triage/SKILL.md
What it does
Triage a Playwright bug report by reproducing it from the information in the issue. Use when asked to triage, reproduce, or verify a GitHub issue (a new bug report, or an existing report with a new comment).
Skill instructions
Playwright Issue Triage Triage a GitHub issue by working out what it actually is, then doing the right thing for that kind. The goal is a clear, verified status, not a fix. First, classify the issue Judge by the content, not the label — a "[Feature]" is often really a bug (something already should work), and a "[Bug]" is sometimes expected behaviour. Work out what it actually is: - Bug — reproduce it. The bulk of this skill. - Feature request — nothing to reproduce. Check it doesn't already exist (search docs/API, maybe under another name), verify any source the reporter cites by reading it, and surface the real design question. If it's small and well-scoped (like "fail loudly instead of silently"), the ideal takeaway is an acceptance test: one self-contained spec asserting current behaviour (passes today) with the desired behaviour alongside as a fixme/commented assertion. - Upstream / environment — a genuinely external owner (the Node project, a browser engine, a website's own server
Explore related resources
Frequently asked questions
What is playwright-triage?
playwright-triage is a open-source AI agent skill with Copy skill directory. Triage a Playwright bug report by reproducing it from the information in the issue.
Who is playwright-triage best for?
playwright-triage is best for reusing agent instructions, scripts, and references, browser automation workflows, testing workflows, documentation workflows.
How do I install playwright-triage?
Install or run playwright-triage using Copy skill directory. Check playwright-triage for the latest setup command.
Is playwright-triage actively maintained?
playwright-triage may need a closer maintenance check before production use.
Auto-fetched from GitHub.
