CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/winappdriver

Authors and runs Windows UI tests against WinAppDriver, Microsoft's W3C-WebDriver service for UWP / WPF / WinForms / Win32 apps: installing + launching `WinAppDriver.exe` on `127.0.0.1:4723`, declaring `app` / `platformName` / `appArguments` / `appTopLevelWindow` capabilities, finding elements by `AccessibilityId` / `Name` / `ClassName`, and Windows-runner CI. Use when driving a native Windows app from a Selenium-style client (C#, Java, Python, Ruby, JS); for the actively-maintained Appium 2.x wrapper over the same server use appium-windows-driver, for a C#-only FlaUI client use flaui-tests, and to choose among Windows desktop drivers first use desktop-test-strategy-reference.

79

Quality

99%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

Overview
Quality
Evals
Security
Files

Quality

Content

100%

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

A well-structured skill body that pairs a concise overview with executable code, concrete tables, and clear multi-step sequencing, and correctly delegates deep detail to a single one-level-deep reference file. It earns top scores on all four content dimensions with only minor description/body repetition as a conciseness nit.

DimensionReasoningScore

Conciseness

The body is dense reference material — capabilities table, a copy-paste C# worked example, an anti-patterns table, and a limitations list — with no filler explanations of concepts Claude already knows; the only drag is mild repetition of the description in the Overview, which is insufficient to drop below 'lean and efficient'.

3 / 3

Actionability

Provides fully executable guidance: a copy-paste launch command, a complete C# worked example resolving an element by AccessibilityId and driving it end to end, a concrete capabilities table, and copy-paste CI steps — matching 'Fully executable code/commands; copy-paste ready'.

3 / 3

Workflow Clarity

The 'How to use' section gives a clear 5-step sequence (Install, Launch, Declare capabilities, Author test, Run on CI) where each step maps to a named detailed section; the operation is non-destructive so the validation-cap-at-2 rule does not apply, and the anti-patterns table provides error-recovery guidance.

3 / 3

Progressive Disclosure

SKILL.md is an overview that offloads the deep reference (full locator-strategy table, Inspect.exe discovery, custom bindings, attach-to-running-window, CI wiring) to references/locators-and-ci.md — a single one-level-deep, clearly signaled link to a verified, well-organized file.

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.

A tightly written, highly specific description that names concrete actions, an explicit Use-when trigger in third-person voice, and clear disambiguation from sibling Windows-driver skills. It satisfies every dimension at the top anchor with no verbosity or over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'installing + launching WinAppDriver.exe on 127.0.0.1:4723', 'declaring app / platformName / appArguments / appTopLevelWindow capabilities', 'finding elements by AccessibilityId / Name / ClassName', and 'Windows-runner CI' — matching the 'Lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly answers both 'what' (authors and runs Windows UI tests with enumerated concrete actions) and 'when' ('Use when driving a native Windows app from a Selenium-style client'), satisfying the 'clearly answers both what AND when with explicit triggers' anchor; not below 3 because the Use-when clause is present and explicit.

3 / 3

Trigger Term Quality

Covers natural terms a user would say — 'WinAppDriver', 'Windows UI tests', 'native Windows app', 'Selenium-style client' — with the prominent skill name as the primary trigger; not below 3 because the variations are well covered rather than missing common forms.

3 / 3

Distinctiveness Conflict Risk

Has a clear niche (direct-to-WinAppDriver.exe Selenium-style automation) and explicitly routes adjacent cases to 'appium-windows-driver', 'flaui-tests', and 'desktop-test-strategy-reference', making it unlikely to trigger for the wrong skill.

3 / 3

Total

12

/

12

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Reviewed

Table of Contents