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.
Install with Tessl CLI
npx tessl i github:boisenoise/skills-collections --skill webapp-testing94
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/skillEvaluation — 100%
↑ 2.17xAgent success when using this skill
Validation for skill structure
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...') and could benefit from more natural user-facing keywords to improve discoverability when users ask about testing their web apps.
Suggestions
Add a 'Use when...' clause with trigger terms like 'test my web app', 'check the frontend', 'browser automation', or 'e2e testing'
Include common user phrases and file/technology variations such as 'localhost', 'dev server', 'React/Vue/Angular app', or 'UI tests'
| 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', 'browser logs', but missing common user terms like 'test my app', 'check the UI', 'e2e testing', 'automation', or 'headless browser'. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'Playwright' and 'local web applications' creates a clear niche. The combination of browser testing, screenshots, and logs is distinct and unlikely to conflict with generic coding 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 through a clear decision tree and complete code examples. The emphasis on using helper scripts as black boxes and the explicit warning about the networkidle pitfall demonstrate thoughtful workflow design.
| 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 for both single and multiple server scenarios. The Playwright script examples are complete and runnable, not pseudocode. | 3 / 3 |
Workflow Clarity | The decision tree clearly sequences the approach based on context (static vs dynamic, server running vs not). The reconnaissance-then-action pattern provides explicit steps with the critical 'networkidle' checkpoint clearly marked. | 3 / 3 |
Progressive Disclosure | Well-structured with clear sections, appropriate use of the decision tree for quick navigation, and references to example files for deeper patterns. Content is appropriately split between overview and referenced examples. | 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.
- 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.