Battle-tested Playwright patterns for writing and debugging reliable E2E, API, component, visual, accessibility, and security tests. Use when you need locator strategy, assertions, fixtures, network mocking, auth flows, trace debugging, or framework recipes for React, Next.js, Vue, and Angular. TypeScript and JavaScript.
Directory
Check a skill beforeyou install it.
Public agent skills get a grade from A to F. See what the scan found and which tools they work in.
- C testdino-hq/playwright-skill playwright-core
- A testdino-hq/playwright-skill playwright-skill
- A testdino-hq/playwright-skill playwright-qa
- A testdino-hq/playwright-skill playwright-pom
- A testdino-hq/playwright-skill playwright-cli
- A testdino-hq/playwright-skill playwright-migration
- A testdino-hq/playwright-skill playwright-frontend
- D testdino-hq/playwright-skill playwright-ci
- D fjkiani/crm-deployment scap_working
- C harrysayers7/cursor-rules 04-git-hooks-automation
What it is
A free directory of public AI agent skill files
It covers SKILL.md, AGENTS.md, Cursor rules, Claude skills, and similar files. Looking them up is free.
Each listing shows:
- An automatic grade from A to F
- Why it got that grade
- Which tools it works in (Claude Code, Cursor, Codex, Gemini CLI)
- A link to the public source
- When we last scanned it
We read the file. We do not run the skill on your machine.
The crawler keeps searching GitHub. When it finds a listed file has changed, it grades it again. Skill pages show the last scan time.
Public registries grew fast with almost no vetting. One study found 157 malicious skills out of 98,380 on registries (Liu et al., 2026).
Grades here come from an automated scan, and it can miss things. An A means the scan found no problem in the text. It doesn't mean nothing's there.
Grades
What the letters mean
Full detail on How the scan works.
Remote script fetch-and-run, or secrets sent out.
Grade D: RiskyHidden code or text, or tells the agent to skip asking you or ignore its own rules.
Grade C: CautionHardcoded keys, sudo, chmod 777, or writes outside the project.
Grade B: Mostly fineA few small flags. Read the reasons before you install.
Grade A: No problem foundThe scan flagged nothing in the file. A small deduction, like no license, can still apply.
Small deductions also apply for no license, 12+ months abandoned, or a brand-new account.
Recently scanned
New this week
Current Playwright (1.64) patterns for writing, debugging, and scaling reliable test suites. Use for any Playwright task, even ones you think you know, because the guides cover APIs and CLI flags newer than most training data. Covers writing or fixing tests, locators, a failing or flaky test, a trace.zip or error message, playwright.config and projects, network mocking, auth, visual and accessibility testing, Docker and CI sharding, playwright-cli browser automation, Playwright Test Agents, pag…
QA engineering workflows on top of Playwright. Use when a QA engineer asks to design test cases from a ticket, PRD or acceptance criteria, decide what to automate, write a bug report from a failing test or trace, convert manual test cases (TestRail, Xray, CSV) into Playwright specs with case-ID traceability, or review Playwright test code and pull requests.
Page Object Model patterns for Playwright — when to use POM, how to structure page objects, and when fixtures or helpers are a better fit.
Automates browser interactions for testing and validating your own web applications using playwright-cli. Use when you need terminal-first browser control for navigation, form filling, screenshots, tracing, bound browser sessions, debugging, or generating Playwright test code. Only use against applications you own or have explicit authorization to test.
Step-by-step migration guides for moving to Playwright from Cypress or Selenium/WebDriver — command mappings, architecture changes, and incremental adoption strategies.
The Grade Report
Weekly grades in your inbox.
New skills, top skills, and risky ones we found. Short mail, once a week.
No spam. Unsubscribe any time.