Install
$ agentstack add skill-erikfiala-e2e-tester-tester ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
E2E Playwright + Lighthouse Tester
Use this skill to run reproducible e2e and Lighthouse checks across a target web repo, with discovery-first command selection and clear reporting.
Workflow
- Discover first
- Run:
python3 .cursor/skills/tester/scripts/discover_audit_targets.py .- Optional JSON output:
python3 .cursor/skills/tester/scripts/discover_audit_targets.py . --json - Read discovered package scripts, runner files, and PWA signals before deciding what to run.
- Runner selection priority
- Prefer existing
npm/pnpm/yarnscripts that already run Playwright and Lighthouse. - Otherwise use checked-in runner files in common locations (
perf/,scripts/,e2e/,tests/). - Only use ad-hoc
npx playwright/npx lighthousecommands if no native runner exists.
- Execution matrix
- For Lighthouse, target all slices when technically possible:
light-desktoplight-mobiledark-desktopdark-mobile- Attempt categories:
performanceaccessibilitybest-practicesseopwa(when supported by installed Lighthouse and app signals)- Prefer preview or production-like mode instead of noisy local dev mode when the repo supports it.
- 100/100 objective
- Always optimize toward 100/100 in Lighthouse categories and Web Vitals-related audits.
- Do not claim false success; explicitly list blockers and remaining deltas to 100.
Reporting contract
Always report by package/surface:
- Commands run, including whether native or adapted.
- Playwright findings: failing flows, flaky clues, console/page errors, failed requests, auth blockers.
- Lighthouse findings per matrix slice (
light-desktop,light-mobile,dark-desktop,dark-mobile). - A dedicated 100/100 gap analysis section with highest impact opportunities.
- Explicit coverage gaps (skipped routes, no dark mode, no mobile emulation, missing credentials, unsupported PWA category).
Guardrails
- Keep commands non-interactive whenever possible.
- Never silently skip a matrix slice; report why it was skipped.
- If the repository is not a web app, stop quickly and state that no web target was detected.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: erikfiala
- Source: erikfiala/e2e-tester
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.