CtrlK
BlogDocsLog inGet started
Tessl Logo

agui-playwright-validate

Manually validate a running web app or docs site with the Playwright MCP server — navigate pages, assert headings/text/status, check for console errors, hover/click to exercise interactions, take screenshots for human review, and verify visual details such as an icon's color in light vs dark mode by reading computed styles. USE FOR: "validate with Playwright", "open the browser and check", visually verifying a UI or docs change, confirming a CSS/SVG/icon edit rendered, checking a page for console errors, comparing light/dark mode appearance. DO NOT USE FOR: writing automated unit/E2E test files (dojo e2e lives in agui-dojo); docs-site content/structure checks specific to the .NET SDK docs (use agui-dotnet-sdk-docs). INVOKES: browser_navigate, browser_snapshot, browser_take_screenshot, browser_evaluate, browser_hover, browser_click, browser_console_messages Playwright MCP tools.

80

Quality

100%

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

SKILL.md
Quality
Evals
Security

Quality

Content

100%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 content is a tight, executable manual-validation playbook: efficient prose, concrete code, a clear cheap-to-expensive workflow with validation checkpoints and recovery loops, and clean organization with no unnecessary external references.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it never explains what Playwright or a browser is, and every section (validation loop, computed-style technique, cache-busting, overlays, cleanup, anti-patterns) earns its tokens with no padding.

5 / 5

Actionability

It provides copy-paste-ready JS (getComputedStyle comparison, classList.toggle('dark'), location.reload(true)), specific tool names (browser_snapshot, browser_console_messages, browser_press_key Escape), and concrete tactics (cache-bust via ?v=<timestamp>) covering the common validation cases.

5 / 5

Workflow Clarity

The 'Validation loop' is a clearly sequenced Navigate → Snapshot → Console → Screenshot → Report flow with explicit checkpoints (confirm heading before screenshotting, assert 0 console errors every page) and recovery loops (Escape to dismiss overlays then retry; hard reload for stale assets).

5 / 5

Progressive Disclosure

No bundle files exist and none are needed; the body is self-contained with well-organized section headers (When to reach for this, Prerequisites, Validation loop, Techniques that matter, Cleanup discipline, Anti-patterns) and nothing inlined that belongs in a separate file.

5 / 5

Total

20

/

20

Passed

Description

100%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 exemplary: concrete actions, natural trigger phrases, explicit what-and-when guidance, and clear boundary disambiguation against related skills. It drives activation precisely with no fluff.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'navigate pages, assert headings/text/status, check for console errors, hover/click to exercise interactions, take screenshots', 'verify visual details such as an icon's color ... by reading computed styles' — giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

It explicitly answers both what (the enumerated validation actions and INVOKES tool list) and when (the 'USE FOR' trigger phrases), plus boundary guidance via 'DO NOT USE FOR' — matching the anchor for explicit what-and-when with concrete triggers.

5 / 5

Trigger Term Quality

The 'USE FOR' clause supplies natural user phrases ('validate with Playwright', 'open the browser and check', 'visually verifying a UI or docs change', 'comparing light/dark mode appearance') with synonyms and variations a user would actually say.

5 / 5

Distinctiveness Conflict Risk

A clear niche (manual Playwright MCP validation of a live app/docs site) is reinforced by explicit disambiguation — 'DO NOT USE FOR ... agui-dojo' and 'use agui-dotnet-sdk-docs' — minimizing overlap with sibling skills.

5 / 5

Total

20

/

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
ag-ui-protocol/ag-ui
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.