CtrlK
BlogDocsLog inGet started
Tessl Logo

webapp-testing

To test local web applications, write native Python Playwright scripts.

55

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/webapp-testing/SKILL.md

The canonical home for this skill is webapp-testing in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

71%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-sequenced with a useful decision tree and executable examples, scoring well on conciseness, actionability, and workflow clarity. Its main weakness is broken progressive disclosure: the examples/ references point to files that are absent from the bundle.

Suggestions

Create the missing examples/ directory with element_discovery.py, static_html_automation.py, and console_logging.py (or remove the Reference Files section) so referenced paths resolve.

Replace the vacuous 'When to Use' line ('This skill is applicable to execute the workflow...') with concrete trigger conditions.

Remove the opening line that duplicates the frontmatter description to tighten token efficiency and fix the 'abslutely' typo.

DimensionReasoningScore

Conciseness

The body is mostly lean, with a compact decision tree and executable examples that assume Claude's competence; minor trimmable padding exists (the opening line repeats the description verbatim, a vacuous 'When to Use' line, and a typo 'abslutely'), keeping it just below a 5.

4 / 5

Actionability

It provides copy-paste-ready bash commands for single and multi-server setups plus an executable Playwright snippet and concrete recon code; it is not a 5 because the Python example leaves a '# ... your automation logic' placeholder gap.

4 / 5

Workflow Clarity

The decision tree gives explicit success/fail branching and the reconnaissance pattern is a clear numbered sequence with a networkidle checkpoint; not a 5 because there is no validate->fix->retry feedback loop for error recovery.

4 / 5

Progressive Disclosure

Structure is reasonably organized and the scripts/with_server.py reference resolves to a real file, but the 'Reference Files' section points to an examples/ directory and three files (element_discovery.py, static_html_automation.py, console_logging.py) that do not exist in the bundle, so navigation is broken and it cannot reach 4.

3 / 5

Total

15

/

20

Passed

Description

53%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 states a clear domain and one concrete action but is terse, lacks an explicit 'Use when' trigger clause, and underuses natural keyword variations. It carves out a fairly distinct niche but would benefit from explicit trigger guidance and broader terminology.

Suggestions

Add an explicit 'Use when...' clause (e.g., 'Use when testing local web apps, automating browser flows, or doing E2E checks') to lift completeness above 3.

Expand natural trigger terms with synonyms users actually say (e.g., 'browser automation', 'E2E testing', 'web app') to improve trigger term quality.

Rephrase in third-person voice (e.g., 'Tests local web applications by writing native Python Playwright scripts') instead of the imperative 'write' form.

DimensionReasoningScore

Specificity

It names the domain ("test local web applications") and one concrete action ("write native Python Playwright scripts"), matching the anchor for naming a domain plus 1-2 concrete actions without comprehensive coverage; it is not a 4 because only a single action is listed rather than several.

3 / 5

Completeness

It clearly states what the skill does (write Playwright scripts to test local web apps) but lacks any "Use when..." clause, so completeness is capped at 3 per the guidelines; not a 4 because the "when" is only weakly implied rather than explicit.

3 / 5

Trigger Term Quality

It includes relevant keywords ("test", "web applications", "Playwright") but misses common variations users say ("browser automation", "E2E testing", "web app"), fitting the anchor for some relevant keywords with missing synonyms; not a 4 given the terse single sentence limits keyword coverage.

3 / 5

Distinctiveness Conflict Risk

The niche (Python Playwright for local web-app testing) is mostly distinct with only minor overlap risk against general web skills; not a 5 because there is no explicit trigger phrase establishing a clear, conflict-free niche.

4 / 5

Total

13

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-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.