CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

webapp-testing

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

Quality

72%

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

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.

A highly actionable, well-structured skill body with copy-paste-ready commands and a clear decision tree. Its main defects are a Reference Files section pointing at nonexistent example files, a boilerplate 'When to Use' section that adds no information, and the absence of an explicit post-action verification step.

Suggestions

Create the referenced examples/ files (element_discovery.py, static_html_automation.py, console_logging.py) or remove the Reference Files section so no navigation path dead-ends.

Replace the boilerplate 'When to Use' sentence with concrete trigger guidance (e.g., when the user asks to test a locally running app, verify a frontend change, or drive a browser on localhost) or delete the section.

Add an explicit verification step after executing actions, such as taking a screenshot or asserting on the resulting DOM state, to close the workflow's feedback loop.

DimensionReasoningScore

Conciseness

The body is dominated by lean, purposeful code and commands, but the 'When to Use' section ('This skill is applicable to execute the workflow or actions described in the overview.') is boilerplate filler, the opening line duplicates the frontmatter description, and the script warning paragraph is wordy.

4 / 5

Actionability

Copy-paste-ready commands ('python scripts/with_server.py --server "npm run dev" --port 5173 -- python your_automation.py') and a fully executable Playwright template with concrete waits and launch options cover the common cases (static HTML, dynamic app, single/multiple servers).

5 / 5

Workflow Clarity

The decision tree sequences static-vs-dynamic and server-running branches with a feedback edge ('Fails/Incomplete → Treat as dynamic'), plus a numbered reconnaissance pattern and a networkidle pitfall guard. Not 5 because there is no explicit validation checkpoint after executing actions (e.g., screenshot or assert to confirm the action succeeded).

4 / 5

Progressive Disclosure

Sections are well organized and 'scripts/with_server.py' exists and is correctly referenced one level deep, but the 'Reference Files' section lists 'examples/element_discovery.py', 'examples/static_html_automation.py', and 'examples/console_logging.py' — none of which exist in the bundle, leaving dangling references that break navigation.

3 / 5

Total

16

/

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 is concise and names a distinct niche, but it is a single-sentence 'what' with no 'when' clause and thin keyword coverage. Adding trigger guidance and natural synonyms would materially improve both completeness and trigger-term quality.

Suggestions

Add a 'Use when...' clause, e.g., 'Use when the user asks to test a locally running web app, verify frontend behavior, or automate browser interactions on localhost.'

Include natural synonyms such as 'end-to-end (e2e) testing', 'UI testing', and 'browser automation' so users' phrasing matches the trigger terms.

Mention one or two more concrete capabilities reflected in the body, such as server lifecycle management, element discovery, or console log capture.

DimensionReasoningScore

Specificity

The description names the domain ('test local web applications') and one concrete approach ('write native Python Playwright scripts'), matching the 1-2 concrete actions anchor; not 4 because it lists only a single action rather than several specific actions.

3 / 5

Completeness

The 'what' is clear (test local web apps by writing Python Playwright scripts), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

It includes relevant keywords ('test', 'local web applications', 'Python Playwright') but misses common natural variations users would say such as 'end-to-end', 'e2e', 'UI testing', or 'browser automation'.

3 / 5

Distinctiveness Conflict Risk

'Local web applications' plus 'native Python Playwright scripts' carves a fairly distinct testing niche with tool-level specificity; minor overlap risk remains with general browser-automation or app-running skills.

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.

Validation — 15 / 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

Path

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

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.