playwright-kit-ops

Run Playwright E2E test scripts for a11y scans, CWV measurement, and Drive evidence upload.

1|Updated Apr 21, 2026
One-click install
npx skills add https://github.com/devbasex/ai-plugins --skill playwright-kit-ops-devbasex
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: playwright-kit-ops
Source: https://github.com/devbasex/ai-plugins/tree/main/plugins/playwright-kit/skills/playwright-kit-ops
Command: npx skills add https://github.com/devbasex/ai-plugins --skill playwright-kit-ops-devbasex

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires playwright, pyyaml, imageio-ffmpeg, pytest, pytest-playwright, pytest-xdist, axe-playwright-python, google-api-python-client, google-auth, google-auth-oauthlib, and includes scripts (resource) components.

What problem does it solve? Setting up and operating Playwright-based E2E scenario tests involves many manual steps: embedding a test runtime into a project, classifying page roles, running accessibility and Core Web Vitals scans, and uploading evidence to Google Drive. This Skill consolidates those operations into a single script-driven workflow. ## Core Features & Use Cases - Project Initialization: Embed a self-contained scenario-test runtime (pytest-playwright based) into any user project via init_project.sh, after which tests run independently of the Skill. - Quality Scans: Run axe-core accessibility scans (WCAG 2.0/2.1/2.2 AA) and Core Web Vitals measurements (LCP/CLS/TTFB) against any URL, plus page-role classification from DOM role analysis. - Evidence Management: Upload traces, HAR files, videos, and Markdown reports to Google Drive, including conversion of report.md into a Google Doc with embedded Drive links. - Use Case: After initializing a project, run ./scenario-test/run.sh --pwk-drive-folder=<ID> to execute all E2E tests with video/trace evidence and automatically upload results to a Drive folder. ## Quick Start Initialize the scenario-test runtime in my project at /path/to/your-app and then run an accessibility scan against https://example.com.

Frequently Asked Questions about playwright-kit-ops

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up Playwright E2E tests in an existing project?▼

Run scripts/init_project.sh with your project root path to embed a self-contained scenario-test runtime. It copies the playwright_kit package, templates, and config, then runs uv sync and playwright install chromium. Afterward, tests run via ./scenario-test/run.sh without depending on the Skill.

How do I run an accessibility scan on a URL with axe-core?▼

Run python scripts/run_a11y_scan.py --url <URL> to perform a single axe-core scan. It checks WCAG 2.0/2.1/2.2 AA tags by default and requires the axe-playwright-python package, which is included as a main dependency.

How do I measure Core Web Vitals with Playwright?▼

Run python scripts/check_cwv.py --url <URL> to measure LCP, CLS, TTFB, and longest task. It supports device emulation via --device, batch URLs via --url-list, and can exit with code 1 on poor ratings using --fail-on-poor.

Does the Google Drive upload require extra setup?▼

Yes, Drive integration is an optional dependency. Install with uv sync --extra drive and set GOOGLE_AUTH_SCRIPTS to the google-auth skill's scripts directory from a cloned ai-plugins repository, since google-auth ships in a separate plugin.

Can I run the tests on Windows?▼

Yes, scripts/init_project.bat provides Windows initialization equivalent to the shell script. The generated runtime also includes run.bat alongside run.sh for executing tests on Windows environments.

Why does the Drive upload fail with a google_auth import error?▼

The uploader scripts cannot locate google_auth.py on sys.path. Set the GOOGLE_AUTH_SCRIPTS environment variable to the google-auth scripts directory, or install the google-auth skill into one of the standard runtime locations the helper searches.