playwright-best-practices
Review Playwright TypeScript Tests
Flaky Playwright tests slow releases and reduce trust in automation. This skill reviews tests against focused TypeScript best practices and suggests concrete fixes.
Stop for confirmation before installing.
Review the plan and obtain explicit user consent before changing files.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "playwright-best-practices" from https://skillstore.io/skills/vitalics-playwright-best-practices.md and its manifest at https://skillstore.io/api/skills/vitalics-playwright-best-practices/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "playwright-best-practices". Review tests/login.spec.ts for flaky patterns.
Expected outcome:
- tests/login.spec.ts:18 uses a fixed delay. Replace it with an action or assertion that auto-waits.
- tests/login.spec.ts:31 checks text after reading it once. Use a web-first text assertion instead.
Using "playwright-best-practices". Check tests/cart.spec.ts for locator quality.
Expected outcome:
- tests/cart.spec.ts:12 uses a structural selector. Prefer a role locator with the visible button name.
- tests/cart.spec.ts:44 depends on item order. Scope the locator to the cart row before clicking.
Using "playwright-best-practices". Audit tests/fixtures for parallel readiness.
Expected outcome:
- tests/fixtures/users.ts:9 creates shared state across workers. Generate isolated users for each test.
- tests/fixtures/users.ts:26 lacks teardown. Delete created records after each test fixture completes.
Security Audit
High RiskMost static findings are false positives from Markdown examples, including example URLs, template literals, relative imports, CI flags, and Playwright API mocks. One real issue remains: SKILL.md requires fetching mutable remote guidelines and treating them as instructions, which can change outside the audited package.
Confirmed security concerns (1)
Capability review items (1)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Risk Factors
โ๏ธ External commands (58)
๐ Network access (181)
๐ Filesystem access (28)
๐ Env variables (32)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/vitalics-playwright-best-practices/audits/7?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/vitalics-playwright-best-practices?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/vitalics-playwright-best-practices?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/vitalics-playwright-best-practices/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/vitalics-playwright-best-practices.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA ยท BibTeX ยท CFF)
APA citation
vitalics. (2026). playwright-best-practices security audit report (audit version 7) [Author version 1.0.0]. Skillstore. https://skillstore.io/skills/vitalics-playwright-best-practices/audits/7BibTeX citation
@techreport{vitalics-vitalics-playwright-best-practices-2026,
author = {vitalics},
title = {playwright-best-practices security audit report (audit version 7)},
institution = {Skillstore},
year = {2026},
number = {7},
url = {https://skillstore.io/skills/vitalics-playwright-best-practices/audits/7},
note = {Author version 1.0.0}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "playwright-best-practices security audit report (audit version 7)"
version: "1.0.0"
type: report
authors:
- name: "vitalics"
date-released: "2026-07-07"
url: "https://skillstore.io/skills/vitalics-playwright-best-practices/audits/7"
identifiers:
- type: other
value: "skillstore:vitalics-playwright-best-practices:audit:7"
description: "Skillstore immutable audit report identifier"
Compare variants
2 installable variantsEach author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.
Why this variant is first
0xbigboss-playwright-best-practices
2026-08-21
vitalics-playwright-best-practices
2026-08-21
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Stabilize Flaky Test Suites
Find manual waits, race-prone assertions, and shared test state before they fail in continuous integration.
Review Pull Requests
Check new Playwright tests for readable locators, clear assertions, and maintainable page object usage.
Standardize Automation Patterns
Apply consistent fixture, sharding, isolation, and API mocking practices across a larger test suite.
Try These Prompts
Review my Playwright test file for best practice issues: <file path>.
Check <file path> for brittle locators, weak assertions, and missing web-first assertions.
Review the Playwright fixtures in <folder> and suggest changes for isolation, reuse, and cleanup.
Audit <test folder> for page objects, parallel execution, sharding readiness, API mocking, and long-term maintainability.
Best Practices
- Provide the exact test files or folders that need review.
- Ask for findings with file and line references for easier triage.
- Apply recommendations with small changes, then rerun the affected tests.
Avoid
- Requesting a broad review without sharing test files or paths.
- Using the skill as a substitute for running Playwright tests.
- Ignoring accessibility names when adopting role-based locator advice.
Frequently Asked Questions
What test framework does this skill target?
Can it rewrite my tests automatically?
Does it execute Playwright tests?
What issues can it find?
Does it support JavaScript tests?
Is remote guideline fetching required?
Developer Details
Author
vitalicsLicense
MIT
Author version
v1.0.0
Skillstore revision
r1
Repository
https://github.com/vitalics/playwright-labs/tree/main/packages/playwright-best-practices/Ref
36e07d5e13068e5be64447e8f20b427cf2cbd21a
Maintenance freshness
7/18/2026
Usage
12 downloads ยท 205 views
File structure
๐ rules/
๐ _sections.md
๐ _template.md
๐ debug-test-steps.md
๐ fixture-custom-merge-reuse.md
๐ fixture-describe-blocks.md
๐ parallel-test-isolation.md
๐ parallel-test-sharding.md
๐ speed-page-object-model.md
๐ AGENTS.md
๐ README.md
๐ SKILL.md