Pom
Skill up1/demo-api-testing-with-playwright-skill/.agents/skills/playwright-skill/pom
API testing with Playwright Skill
npx -y skills add up1/demo-api-testing-with-playwright-skill --skill pomAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Page Object Model patterns for Playwright — when to use POM, how to structure page objects, and when fixtures or helpers are a better fit.
SKILL.md
0.7 KB, as published. Nobody here has run it
Playwright Page Object Model
Structure your test code for maintainability — know when POM helps and when simpler patterns win.
2 guides covering Page Object Model implementation and the decision framework for choosing between POM, fixtures, and helpers.
Guide Index
| Topic | Guide |
|---|---|
| Page Object Model patterns | page-object-model.md |
| POM vs fixtures vs helpers | pom-vs-fixtures-vs-helpers.md |
Gives 1 of the 12 instructions most e2e browser skills give
Counted across 407 of the 410 authors here whose files we hold, read 2026-08-06
- use page object model patternhere, and in 35 of 407, across 25 files
- Snapshot to get element refsin 24 of 407, across 14 files
- keep tests independentin 23 of 407, across 18 files
- Interact using refs from the latest snapshotin 23 of 407, across 11 files
- clean up test data after each testin 21 of 407, across 15 files
- test user behavior not implementationin 20 of 407, across 14 files
- quarantine flaky tests explicitlyin 19 of 407, across 10 files
- wait for specific network conditionsin 18 of 407, across 8 files
- re-snapshot after navigation or dom changesin 17 of 407, across 10 files
- Detect running dev servers before writing test codein 17 of 407, across 7 files
- use web-first assertionsin 17 of 407, across 14 files
- capture screenshots or videos on test failurein 17 of 407, across 14 files
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.