webapp-testing
Test local web applications with Playwright. Use when asked to verify frontend functionality, debug UI behavior, capture browser screenshots, or inspect browser logs.
Install with Tessl CLI
npx tessl i github:warpdotdev/oz-skills --skill webapp-testing99
Does it follow best practices?
Validation 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 a well-crafted skill description that follows best practices. It uses third person voice, specifies the tool (Playwright), lists concrete actions, and includes an explicit 'Use when' clause with natural trigger terms. The description is concise yet comprehensive enough to distinguish it from other testing or automation skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'verify frontend functionality', 'debug UI behavior', 'capture browser screenshots', 'inspect browser logs'. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Test local web applications with Playwright') and when ('Use when asked to verify frontend functionality, debug UI behavior, capture browser screenshots, or inspect browser logs') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'web applications', 'Playwright', 'frontend', 'UI', 'browser screenshots', 'browser logs'. Good coverage of terms a developer would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused on Playwright browser testing for local web apps. The combination of 'Playwright', 'browser screenshots', and 'browser logs' creates distinct triggers unlikely to conflict with general testing or other automation skills. | 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 excellent skill file that efficiently teaches web application testing with Playwright. It provides a clear decision tree for choosing approaches, executable code examples, and properly highlights the critical networkidle pitfall. The structure balances quick-start guidance with references to detailed examples.
| 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 browsers work—jumps straight to actionable patterns. | 3 / 3 |
Actionability | Provides fully executable code examples with specific commands for both single and multiple server scenarios. The Playwright script examples are copy-paste ready with concrete selectors and methods. | 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 wait highlighted as a validation checkpoint. | 3 / 3 |
Progressive Disclosure | Well-structured with clear sections and appropriate references to helper scripts and example files. Content is appropriately split between the main skill file and referenced examples in examples/ directory with clear navigation. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
87%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 14 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs | Warning |
Total | 14 / 16 Passed | |
- 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.