CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

90

2.17x
Quality

71%

Does it follow best practices?

Impact

100%

2.17x

Average score across 7 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/browser-and-automation/webapp-testing/SKILL.md

The canonical home for this skill is webapp-testing in anthropics/skills

SKILL.md
Quality
Evals
Security

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a well-structured skill that provides clear, actionable guidance for web application testing with Playwright. The decision tree is an effective way to guide approach selection, and the code examples are executable and practical. Minor verbosity in best practices and some redundant advice slightly reduce token efficiency, but overall the skill is strong.

Suggestions

Trim the 'Best Practices' section by removing advice Claude already knows (e.g., 'Always close the browser when done', 'Use sync_playwright() for synchronous scripts') to improve conciseness.

DimensionReasoningScore

Conciseness

Mostly efficient but has some unnecessary padding. The 'Best Practices' section includes advice Claude already knows (close browser, use descriptive selectors). The repeated emphasis on running --help and not reading source code is slightly verbose but contextually justified for preventing context pollution.

2 / 3

Actionability

Provides fully executable code examples for server management, Playwright scripting, and the reconnaissance pattern. The with_server.py examples are copy-paste ready with both single and multi-server variants, and the Playwright script template is complete and runnable.

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 a clear 3-step workflow with the critical networkidle wait highlighted as a common pitfall. For a testing/automation skill, the validation is appropriately handled through screenshots and DOM inspection.

3 / 3

Progressive Disclosure

The SKILL.md serves as a clear overview with well-signaled references to examples/ directory with specific file descriptions. Content is appropriately split between the main file (patterns, decision tree, common usage) and referenced examples for specific patterns. References are one level deep and clearly organized.

3 / 3

Total

11

/

12

Passed

Description

57%

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 adequately identifies the tool (Playwright) and its domain (local web application testing) with a reasonable set of capabilities listed. However, it lacks an explicit 'Use when...' clause, which limits its completeness, and the trigger terms could be broader to capture more natural user phrasings like 'e2e testing' or 'headless browser'.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to test, interact with, or debug a local web application, or mentions Playwright, browser automation, or end-to-end testing.'

Include additional natural trigger terms users might say, such as 'e2e testing', 'end-to-end', 'headless browser', 'web automation', 'click button', 'page navigation', or 'DOM inspection'.

DimensionReasoningScore

Specificity

Names the domain (local web applications, Playwright) and several actions (verifying frontend functionality, debugging UI behavior, capturing screenshots, viewing browser logs), but the actions are somewhat general rather than highly concrete operations.

2 / 3

Completeness

Clearly describes what the skill does (interacting with and testing local web apps via Playwright, screenshots, logs), but lacks an explicit 'Use when...' clause specifying when Claude should select this skill, which caps this dimension at 2.

2 / 3

Trigger Term Quality

Includes relevant terms like 'Playwright', 'browser screenshots', 'browser logs', 'frontend', and 'UI', but misses common user-facing variations like 'end-to-end testing', 'e2e', 'headless browser', 'DOM', 'click', 'navigate', or 'web testing'.

2 / 3

Distinctiveness Conflict Risk

The mention of Playwright and the specific combination of local web app testing, browser screenshots, and browser logs creates a clear niche that is unlikely to conflict with other skills like generic testing or document-related skills.

3 / 3

Total

9

/

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
eigent-ai/agent-skills
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.