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%

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

The skill body is concise, concrete, and well-structured: a clear cheap-to-expensive validation loop with checkpoints, executable gotcha-focused techniques, and clean sectioning with no unnecessary reference indirection. No changes needed.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it does not re-explain browsers, MCP, or accessibility trees, and each section (cache-busting, ephemeral ids, overlay interception) earns its place rather than padding.

3 / 3

Actionability

Provides fully executable JS snippets (getComputedStyle comparisons, classList toggle) and specific tool invocations (browser_press_key Escape, cache-busted URL, location.reload(true)), copy-paste ready rather than pseudocode.

3 / 3

Workflow Clarity

The numbered Validation loop (Navigate → Snapshot → Console → Screenshot → Report) is cheap-to-expensive with explicit validation checkpoints ('assert 0 errors', 'Confirm the expected heading... before screenshotting') and a clear stop condition.

3 / 3

Progressive Disclosure

No bundle files exist and none are needed; the single self-contained file is organized into clear, well-signaled sections with no nested references, satisfying the rubric's allowance for skills with no need for external references.

3 / 3

Total

12

/

12

Passed

Description

100%

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 a model example: concrete capabilities, natural trigger terms, explicit when-to-use guidance with exclusion boundaries, and clear differentiation from sibling skills. No changes needed.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — navigate pages, assert headings/text/status, check console errors, hover/click, take screenshots, read computed styles — matching the anchor for listing several specific actions rather than naming a domain only.

3 / 3

Completeness

Explicitly answers both what (concrete validation actions) and when (USE FOR triggers plus DO NOT USE FOR boundaries and INVOKES tools), so both clauses are present and explicit.

3 / 3

Trigger Term Quality

The 'USE FOR' clause supplies natural phrasings a user would say ('validate with Playwright', 'open the browser and check', 'confirming a CSS/SVG/icon edit rendered', 'comparing light/dark mode'), giving good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

The DO NOT USE FOR clause explicitly disambiguates from sibling skills (agui-dojo for E2E tests, agui-dotnet-sdk-docs for .NET docs), carving a clear niche unlikely to trigger the wrong skill.

3 / 3

Total

12

/

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.

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.