agentsclimarketplace

Playwright e2e execution run

Skill Raishin/vanguard-frontier-agentic/skills/qa/playwright-e2e-execution-run

Curated marketplace of AI skills, agents, and rules for cloud, zero-trust, and compliance-aware engineering - works with Claude Code, Codex, Cursor, Copilot, and more.

Install
npx -y skills add Raishin/vanguard-frontier-agentic --skill playwright-e2e-execution-run

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 18 stars18 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

Use this skill when an operator wants to actually execute an existing Playwright end-to-end suite against a confirmed non-production target and receive a structured, attested run report — pass/fail counts, flaky tests, durations, and trace artifacts. Trigger when the user asks to "run the e2e suite", "execute the Playwright tests against staging", or hands the agent a Playwright project plus a target base URL. This is the live-execution counterpart to the static-review skill `playwright-e2e-suite-review`. Default mode is static and runs nothing; runtime execution is a per-session opt-in that requires explicit target confirmation.

SKILL.md

4.5 KB, as published. Nobody here has run it

Playwright E2E Execution Run

Purpose

This skill executes an existing Playwright end-to-end suite against an operator-confirmed non-production target and emits a structured run attestation: total/passed/failed/flaky counts, slowest tests, retry-only passes, and the location of trace and screenshot artifacts. It is the live-execution counterpart to playwright-e2e-suite-review (which is static-review only and never runs anything). The skill runs the suite as authored — it does not write the tests, deploy the application, or mutate infrastructure — and it refuses to run against a production target.

Execution modes

  • Static (default). The skill runs nothing. It inspects playwright.config, enumerates the project and target, states exactly which command it would execute, and asks the operator for explicit runtime opt-in plus target confirmation.
  • Runtime (per-session opt-in). Only after the operator explicitly opts in and confirms a non-production base URL does the skill invoke npx playwright test. Runtime mode is never assumed from the request alone.

Lean operating rules

  • Never execute the suite without an explicit, in-session runtime opt-in AND an operator-confirmed base URL — absent either, stay in static mode and ask.
  • Refuse to run if the target base URL resolves to, or is named like, a production environment (prod, www., a customer-facing apex domain). Require a staging, preview, or ephemeral target; state the refusal reason.
  • Never accept credentials, bearer tokens, or a storageState file inline. Test credentials must come from the environment or a config the operator already controls; the skill never collects, echoes, or logs their values.
  • Run only the allowlisted commands: npx playwright test (with operator-supplied flags), npx playwright install (browser binaries), npx playwright show-report. Never run deploy, migration, seed, or registry commands.
  • Treat the suite's own side effects as the operator's responsibility — state plainly that E2E tests may create or modify data in the target, which is why a non-production target is mandatory.
  • Do not retry a failed run with raised timeouts or added retries to manufacture a green result — report the failure as observed.
  • Emit the run attestation as JSON conforming to schemas/attestation.schema.json; the verdict is one of pass, fail, or manual-review.
  • If browser binaries are missing, run npx playwright install only with operator awareness; if egress to the browser CDN is blocked, degrade to manual-review rather than reporting a false fail.
  • Label the run: command executed, target host (host only, never the full credentialed URL), Playwright version, and wall-clock duration.

References

Load these only when needed:

Response minimum

Return, at minimum:

  • The execution mode used (static or runtime) and why
  • The exact command executed (runtime) or that would be executed (static)
  • The confirmed target host and Playwright version
  • Run results: total / passed / failed / flaky (retry-only pass) counts
  • Trace and screenshot artifact locations for any failure
  • A pass / fail / manual-review verdict with reasons
  • Safe next actions

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.