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.

92

2.17x
Quality

76%

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 ./.agent/skills/webapp-testing/SKILL.md

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

SKILL.md
Quality
Evals
Security

Quality

Content

78%Weight 40%Scale 1-5

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

The body is actionable and well-structured with a useful decision tree, but progressive disclosure is undermined by references to nonexistent example files. Tightening the redundant recon section and adding a retry loop would raise the remaining dimensions.

Suggestions

Create the referenced examples/ files (element_discovery.py, static_html_automation.py, console_logging.py) or remove the 'Reference Files' section to avoid broken references.

Add an explicit validate/retry step in the workflow (e.g. re-check selectors or re-run with adjusted waits when an action fails) to close the feedback loop.

Fix the typo 'abslutely' → 'absolutely' and merge the overlapping content between the decision tree and the Reconnaissance-Then-Action section.

DimensionReasoningScore

Conciseness

Mostly lean and assumes Playwright competence, with the decision tree and copy-paste examples earning their tokens; the Reconnaissance-Then-Action section partially restates the decision tree and could be tightened.

4 / 5

Actionability

Provides copy-paste-ready commands for single and multiple servers plus a complete executable Playwright snippet, covering the common cases directly.

5 / 5

Workflow Clarity

The decision tree sequences the approach with explicit success/fail branches and the recon pattern gives ordered steps, but there is no full validate-fix-retry feedback loop for error recovery.

4 / 5

Progressive Disclosure

The body is well-sectioned and keeps bulk logic in the bundled script, but the 'Reference Files' section points to an examples/ directory (element_discovery.py, static_html_automation.py, console_logging.py) that does not exist in the bundle.

3 / 5

Total

16

/

20

Passed

Description

75%Weight 40%Scale 1-5

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 specific, concrete, and well-differentiated, but it omits any explicit 'Use when...' trigger guidance, which caps its completeness. Adding a trigger clause with synonyms would lift the two weaker dimensions.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when testing local web apps, debugging frontend behavior, or capturing browser screenshots/logs.'

Include natural synonyms and terms users actually say (e.g. 'local web app', 'localhost', 'UI testing') to broaden trigger coverage.

Consider mentioning common dev-server ports or 'npm run dev'/'vite' style triggers to strengthen distinctiveness.

DimensionReasoningScore

Specificity

Names the domain (local web app testing with Playwright) and lists four concrete actions: 'verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs', giving comprehensive coverage.

5 / 5

Completeness

The 'what' is clear and concrete, but there is no 'Use when...' clause or equivalent explicit trigger guidance, so completeness is capped at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Good natural-term coverage ('web applications', 'testing', 'debugging UI', 'browser screenshots', 'browser logs') but lacks synonyms and file extensions users might say, stopping short of comprehensive.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (local web app testing via Playwright) with distinct triggers and minimal overlap risk against other skills.

5 / 5

Total

17

/

20

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Project-N-E-K-O/N.E.K.O
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.