Use when writing E2E tests with Playwright, setting up test infrastructure, or debugging flaky browser tests. Invoke to write test scripts, create page objects, configure test fixtures, set up reporters, add CI integration, implement API mocking, or perform visual regression testing. Trigger terms: Playwright, E2E test, end-to-end, browser testing, automation, UI testing, visual testing, Page Object Model, test flakiness.
95
100%
Does it follow best practices?
Impact
90%
1.23xAverage score across 6 eval scenarios
Passed
No known issues
Quality
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, provides comprehensive specific actions, includes explicit 'Use when' and 'Invoke to' clauses, and lists natural trigger terms that users would actually say. The description clearly distinguishes itself from other testing-related skills by focusing specifically on Playwright and E2E browser testing.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'write test scripts, create page objects, configure test fixtures, set up reporters, add CI integration, implement API mocking, perform visual regression testing' - comprehensive and actionable. | 3 / 3 |
Completeness | Clearly answers both what (write test scripts, create page objects, etc.) AND when ('Use when writing E2E tests with Playwright, setting up test infrastructure, or debugging flaky browser tests') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'Playwright, E2E test, end-to-end, browser testing, automation, UI testing, visual testing, Page Object Model, test flakiness' covers both technical and common variations. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on Playwright E2E testing with distinct triggers like 'Playwright', 'Page Object Model', 'test flakiness' that wouldn't overlap with general testing or other test frameworks. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an exemplary skill file that demonstrates excellent token efficiency while providing comprehensive, actionable guidance. The reference table with contextual loading triggers is particularly well-designed, and the code examples are complete and executable. The debugging workflow with explicit verification steps shows mature understanding of test reliability concerns.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, avoiding explanations of basic concepts Claude already knows. Every section serves a purpose with no padding or unnecessary context about what Playwright or E2E testing is. | 3 / 3 |
Actionability | Provides fully executable TypeScript code examples including complete Page Object implementation, test files, and debugging commands. Code is copy-paste ready with proper imports and realistic scenarios. | 3 / 3 |
Workflow Clarity | The debugging workflow includes explicit numbered steps with validation (run → check trace → identify → fix → verify with 10x repeat). The core workflow is clear, and the MUST DO/MUST NOT DO constraints provide clear guardrails. | 3 / 3 |
Progressive Disclosure | Excellent structure with a reference table pointing to one-level-deep topic files (selectors, POM, API mocking, etc.) with clear 'Load When' guidance. Main content stays focused while detailed guidance is appropriately externalized. | 3 / 3 |
Total | 12 / 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.
5b76101
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.