webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
94
83%
Does it follow best practices?
Impact
100%
2.17xAverage score across 7 eval scenarios
Passed
No known issues
Quality
Discovery
67%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 description effectively communicates specific capabilities for browser-based testing with Playwright, establishing a clear niche. However, it lacks explicit trigger guidance ('Use when...') which limits Claude's ability to know exactly when to select this skill, and could benefit from more natural user-facing trigger terms beyond technical terminology.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when testing web apps, running e2e tests, automating browser interactions, or when the user mentions Playwright, browser testing, or UI verification'
Include additional natural trigger terms users might say: 'e2e testing', 'end-to-end tests', 'browser automation', 'headless testing', 'DOM inspection'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'verifying frontend functionality', 'debugging UI behavior', 'capturing browser screenshots', and 'viewing browser logs'. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers 'what does this do' with specific capabilities, but lacks an explicit 'Use when...' clause or equivalent trigger guidance. The 'when' is only implied through the capability descriptions. | 2 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'Playwright', 'web applications', 'browser screenshots', 'UI', and 'frontend', but missing common variations users might say like 'e2e testing', 'end-to-end', 'browser automation', 'headless browser', or 'DOM testing'. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'Playwright' specifically and the focus on 'local web applications' with browser-specific actions (screenshots, logs) creates a clear niche that is unlikely to conflict with general testing or document skills. | 3 / 3 |
Total | 10 / 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 a high-quality skill that efficiently teaches web application testing with Playwright. It excels at providing concrete, executable guidance while maintaining brevity. The decision tree and reconnaissance-then-action pattern provide clear workflows with appropriate validation checkpoints.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, assuming Claude's competence with Playwright and Python. No unnecessary explanations of what Playwright is or how web servers work - it jumps straight to actionable patterns. | 3 / 3 |
Actionability | Provides fully executable code examples with copy-paste ready commands. The bash examples for with_server.py and Python Playwright scripts are complete and specific, not pseudocode. | 3 / 3 |
Workflow Clarity | The decision tree clearly sequences the approach based on context. The reconnaissance-then-action pattern provides explicit steps with validation (wait for networkidle before inspection). The common pitfall section reinforces the critical checkpoint. | 3 / 3 |
Progressive Disclosure | Well-structured with clear sections. References to scripts/ and examples/ are one level deep and clearly signaled. The instruction to use --help first before reading source code is excellent progressive disclosure. | 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.
- Repository
- ComposioHQ/awesome-claude-skills
- Commit
362d354
- 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.