setup-artillery-playwright-reporter
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.
Install with Tessl CLI
npx tessl i github:artilleryio/agent-skills --skill setup-artillery-playwright-reporter90
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that follows best practices. It uses third person voice, lists specific concrete actions, includes explicit 'Use when' triggers with natural keywords, and targets a clear niche (Artillery + Playwright integration) that minimizes conflict risk with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Installs @artilleryio/playwright-reporter, configures it in playwright.config.ts, sets up Artillery Cloud API key, and runs the suite to verify reporting works.' | 3 / 3 |
Completeness | Clearly answers both what (installs reporter, configures playwright.config.ts, sets up API key, runs verification) AND when ('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'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'Artillery', 'Playwright', 'E2E test', 'reporter', 'Artillery Cloud', 'dashboard', 'Playwright tests'. Good coverage of both tool names and use case terms. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche combining Artillery Cloud with Playwright E2E testing. The specific tool names (@artilleryio/playwright-reporter) and integration context make it highly unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, actionable skill that guides Claude through setting up the Artillery Playwright reporter with clear steps and decision points. The workflow is logical and includes verification. Main weakness is some verbosity in explaining things Claude already knows (package manager commands, basic config patterns) that could be trimmed for token efficiency.
Suggestions
Remove the package manager command table - Claude knows how to install npm packages with different package managers
Condense the 'If reporter exists' vs 'If no reporter exists' sections into a single example with a brief note about merging with existing reporters
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but includes some unnecessary verbosity, such as the full table of package manager commands (Claude knows these) and repetitive explanations. The before/after code examples are helpful but could be more compact. | 2 / 3 |
Actionability | Provides fully executable commands and copy-paste ready TypeScript configuration examples. Each step has concrete code snippets, specific file paths, and exact commands to run. | 3 / 3 |
Workflow Clarity | Clear 5-step sequence with explicit decision points marked for user interaction. The workflow progresses logically from detection to installation to configuration to verification, with appropriate checkpoints at each DECISION marker. | 3 / 3 |
Progressive Disclosure | Content is well-structured with clear sections and headers, but everything is inline in a single file. For a skill of this length (~100 lines), some content like the package manager table or monorepo handling could be referenced separately, though the current organization is acceptable. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Reviewed
Table of Contents
Is this your skill?
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.