writing-playwright-tests
Provides guidance and best practices for writing Playwright E2E tests, including linting and standard patterns.
Install
mkdir -p .claude/skills/writing-playwright-tests && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/1000" && unzip -o skill.zip -d .claude/skills/writing-playwright-tests && rm skill.zipInstalls to .claude/skills/writing-playwright-tests
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Use when writing new Playwright E2E tests or adding test cases. Provides testing philosophy, patterns, and best practices from the Playwright Developer Handbook.Key capabilities
- →Write Playwright E2E test cases
- →Enforce linting rules for test code
- →Implement testing patterns from developer handbook
- →Identify and fix test anti-patterns
How it works
The skill applies specific ESLint rules and architectural patterns defined in the OpenMetadata Playwright Developer Handbook to ensure test reliability and CI compatibility.
Inputs & outputs
When to use writing-playwright-tests
- →Writing new E2E test cases
- →Fixing test anti-patterns
- →Running linting for tests
- →Implementing best practices for UI testing
About writing-playwright-tests
This skill guides the creation of end-to-end tests using Playwright. It enforces linting rules and ensures adherence to specific testing philosophies to improve test reliability.
Use when writing new Playwright E2E tests or adding test cases. Provides testing philosophy, patterns, and best practices from the Playwright Developer Handbook.
When not to use it
- →When writing non-E2E tests
- →When working outside the OpenMetadata codebase
Prerequisites
Limitations
- →Linting rules block CI submission
- →Restricted to OpenMetadata standards
How it compares
It enforces project-specific linting and philosophy standards rather than generic Playwright best practices.
Compared to similar skills
writing-playwright-tests side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| writing-playwright-tests (this skill) | 5 | 5mo | Review | Beginner |
| dependency-upgrade | 26 | 5mo | Review | Intermediate |
| validate-typescript | 5 | 9mo | Review | Beginner |
| ts-testing | 6 | 8mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by open-metadata
View all by open-metadata →You might also like
dependency-upgrade
wshobson
Manage major dependency version upgrades with compatibility analysis, staged rollout, and comprehensive testing. Use when upgrading framework versions, updating major dependencies, or managing breaking changes in libraries.
validate-typescript
BerryKuipers
Run TypeScript compiler type-checking (tsc --noEmit) to validate type safety and catch type errors. Works with any TypeScript project. Returns structured output with error counts, categories (type/syntax/import errors), and affected files. Used for quality gates and pre-commit validation.
ts-testing
johnlindquist
Design, implement, and maintain high‑value TypeScript test suites using popular JS/TS testing libraries. Use this skill whenever the user is adding tests, debugging failing tests, or refactoring code that should be covered by tests.
react-best-practices
redpanda-data
Client-side React performance optimization patterns.
feature-flags
Use when feature flag tests fail, flags need updating, understanding @gate pragmas, debugging channel-specific test failures, or adding new flags to React.
typescript-code-review
anyproto
Perform comprehensive code reviews for TypeScript projects, analyzing type safety, best practices, performance, security, and code quality with actionable feedback