Set up the Artillery Playwright reporter in an existing Playwright E2E test suite. Installs @artilleryio/playwright-reporter, configures it in playwright.config.ts, sets up Artillery Cloud API key, and runs the suite to verify reporting works. Use when the user wants to add Artillery Cloud reporting to their Playwright tests, monitor E2E test results in a dashboard, or integrate Playwright with Artillery Cloud.
100
100%
Does it follow best practices?
Impact
100%
1.36xAverage score across 3 eval scenarios
Passed
No known issues
Reporter config placement and preservation
Correct package install
100%
100%
Dev dependency flag
100%
100%
Correct package manager
100%
100%
Reporter at beginning of array
0%
100%
Existing reporters preserved
100%
100%
Descriptive name property
0%
100%
ARTILLERY_CLOUD_API_KEY referenced
100%
100%
Shell export instruction
100%
100%
Existing test command used
70%
100%
Subsequent run explanation
70%
100%
Monorepo workspace-scoped installation
Monorepo detection
75%
100%
Correct workspace identified
100%
100%
Workspace-scoped install command
100%
100%
Dev dependency flag
100%
100%
Correct package manager
100%
100%
Reporter at beginning of array
0%
100%
Descriptive name property
0%
100%
Existing reporters preserved
100%
100%
ARTILLERY_CLOUD_API_KEY referenced
100%
100%
Config modified in correct workspace
100%
100%
API key setup with .env secret management
Correct env var name
100%
100%
Added to .env file
100%
100%
.gitignore verification
100%
100%
Reporter section created
100%
100%
Reporter at beginning of array
30%
100%
Descriptive name property
0%
100%
Dev dependency install
62%
100%
Correct package manager
50%
100%
Existing test script referenced
100%
100%
Artillery Cloud URL mentioned
20%
100%
78a9dbe
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.