CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

winappdriver

Use when a native Windows app (UWP, WPF, WinForms, Win32) must be driven from a Selenium-style client in C#, Java, Python, Ruby or JS: WinAppDriver directly or through the Appium 2 Windows driver, capabilities, AccessibilityId and Name locators, and Windows CI runners. C#-only: flaui-tests.

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is testland/winappdriver

SKILL.md
Quality
Evals
Security

Quality

Content

86%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 strong, action-oriented body: both invocation paths carry copy-paste-ready code, the workflow is clearly sequenced with failure modes addressed, and deep material is correctly delegated to two real, one-level-deep reference files. The only costs are mild redundancy around maintenance status and time-sensitive version details, and the absence of explicit validation checkpoints in the workflow.

DimensionReasoningScore

Conciseness

The body is dense and table-heavy with no basic-concept tutorials and every section earning its place, but the README quotation in the Overview, the maintenance-status statement duplicated in both "Invoking via Appium" and "Limitations", and version/date details ("v1.2.1, published 2020-11-05") appearing outside a deprecation-style section are minor instances that could be trimmed.

4 / 5

Actionability

Fully executable guidance throughout: the copy-paste cmd launch command, the Appium install/pin command sequence (npm install -g appium through appium --port 4723), a complete runnable C# worked example, a JSON capabilities block, and a Python client example — covering both invocation paths end to end for the common cases.

5 / 5

Workflow Clarity

"How to use" gives a numbered 5-step sequence (Install → Launch → Declare capabilities → Author test → CI) with each step mapping to a section, a service-readiness signal ("Press ENTER to exit."), and Anti-patterns covering failure modes with fixes — but explicit per-step validation checkpoints (e.g., verify session creation before driving elements) are missing.

4 / 5

Progressive Disclosure

Verified against the actual bundle: both references/locators-and-ci.md and references/gestures-hooks-and-ci.md exist, are one level deep, and are repeatedly well-signaled with a description of what lives where; deep content (locator tables, Inspect.exe, CI wiring, gestures, PowerShell hooks) is properly split out, keeping the body a clear overview.

5 / 5

Total

18

/

20

Passed

Description

87%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.

A highly effective description with an explicit and specific trigger clause, concrete tool and framework coverage, and minimal conflict risk. Its only weaknesses are a topic-list framing rather than multiple distinct action verbs and a few missing natural phrasings such as "test automation" or "desktop automation".

DimensionReasoningScore

Specificity

The description enumerates many concrete specifics — both invocation paths ("WinAppDriver directly or through the Appium 2 Windows driver"), "capabilities, AccessibilityId and Name locators, and Windows CI runners", plus the C#-only flaui-tests alternative — but frames them under a single core verb ("must be driven") as a topic list rather than multiple distinct action phrases, leaving minor gaps versus the comprehensive multi-action anchor.

4 / 5

Completeness

It opens with an explicit "Use when a native Windows app (UWP, WPF, WinForms, Win32) must be driven from a Selenium-style client" trigger and then explicitly states the what via the post-colon enumeration of drivers, capabilities, locators, and CI runners — both what and when are concrete and explicit.

5 / 5

Trigger Term Quality

Strong keyword coverage of the exact terms a user with this need would say — "WinAppDriver", "Appium 2 Windows driver", "Selenium-style client", "UWP, WPF, WinForms, Win32", "Windows CI runners" — but common natural phrasings like "test automation", "desktop automation", and "UIA" are absent, so a few natural terms are missing.

4 / 5

Distinctiveness Conflict Risk

A clear niche — driving native Windows apps via WinAppDriver/Appium Windows driver — with distinct tool-name triggers; scoping to native apps (UWP/WPF/WinForms/Win32) excludes browser-automation overlap, and it even disambiguates the adjacent flaui-tests option as C#-only, giving minimal conflict risk.

5 / 5

Total

18

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

testland/qa

Path

plugins/qa-desktop/skills/winappdriver/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.