playwright-testing
E2E testing with Playwright - Page Objects, cross-browser, CI/CD
38
37%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/playwright-testing/SKILL.mdQuality
Discovery
32%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description is a terse comma-separated list of topic keywords rather than a proper skill description. While it names the technology (Playwright) and relevant concepts, it fails to describe concrete actions the skill performs and completely lacks trigger guidance ('Use when...'). It reads more like a tag list than a description that would help Claude reliably select this skill from a large pool.
Suggestions
Add explicit actions describing what the skill does, e.g., 'Generates Playwright E2E test scripts using the Page Object pattern, configures cross-browser test matrices, and sets up CI/CD pipeline integration.'
Add a 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about end-to-end testing, browser automation, Playwright tests, writing .spec.ts files, or setting up test pipelines.'
Include common user-facing synonyms and variations like 'end-to-end', 'browser testing', 'test automation', 'integration testing', '.spec.ts' to improve trigger term coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (E2E testing with Playwright) and mentions some concepts (Page Objects, cross-browser, CI/CD), but these are more like topic labels than concrete actions. It doesn't describe specific actions like 'write test scripts', 'generate page object classes', or 'configure browser matrices'. | 2 / 3 |
Completeness | The description only loosely addresses 'what' through topic keywords and completely lacks a 'when' clause or any explicit trigger guidance. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the 'what' is also weak (just topic labels, not actions), so this scores a 1. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Playwright', 'E2E testing', 'Page Objects', 'cross-browser', and 'CI/CD' which users might mention. However, it misses common variations like 'end-to-end', 'browser testing', 'test automation', 'integration tests', or file extensions like '.spec.ts'. | 2 / 3 |
Distinctiveness Conflict Risk | Mentioning 'Playwright' specifically helps distinguish it from other testing skills (e.g., Cypress, Selenium), but the broad terms 'E2E testing' and 'CI/CD' could overlap with other testing or DevOps skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is highly actionable with excellent, executable code examples covering the full Playwright testing lifecycle. However, it is severely over-long and monolithic — it reads more like comprehensive documentation than a concise skill file. Much of the content (complete page object implementations, full link crawlers, detailed assertion references) is knowledge Claude already possesses and could generate from brief patterns or pointers.
Suggestions
Reduce the document to ~100-150 lines focusing on project-specific conventions, the locator priority order, the auth setup pattern, and anti-patterns — move full page object implementations, link checker code, and CI configs to separate referenced files.
Remove the comprehensive assertions reference section entirely — Claude knows Playwright's assertion API and this is pure documentation duplication.
Add an explicit numbered workflow for setting up E2E testing from scratch with validation checkpoints (e.g., 'Run npx playwright test --project=chromium to verify setup before writing tests').
Split into SKILL.md (overview + key patterns + references) with supporting files like PAGE_OBJECTS.md, CI_CD.md, and LINK_CHECKING.md for the detailed code examples.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~600+ lines. It includes extensive boilerplate code that Claude can generate on its own (full page object implementations, complete CI/CD configs, comprehensive link crawlers). The 'Dead Link Detection (REQUIRED)' section alone is ~100 lines of code that could be summarized in a few lines with a pattern reference. Much of this is reference documentation Claude already knows. | 1 / 3 |
Actionability | Every section provides fully executable, copy-paste ready code examples — from playwright.config.ts to page objects, test files, CI/CD workflows, and CLI commands. The code is complete TypeScript with proper imports and types. | 3 / 3 |
Workflow Clarity | The setup flow (install → configure → write tests → run) is implicit from the document structure but never explicitly sequenced. There are no validation checkpoints (e.g., 'verify browsers installed successfully before proceeding'). The auth setup dependency chain is well-defined in config but the overall workflow for setting up a new test suite lacks explicit sequencing. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of content with no references to external files despite being well over 500 lines. The full page object implementations, complete link crawler code, CI/CD configs, and visual testing examples should be split into separate referenced files. Everything is inline in a single massive document. | 1 / 3 |
Total | 7 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (962 lines); consider splitting into references/ and linking | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Repository
- alinaqi/claude-bootstrap
- Commit
7e5f7a2
- 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.