CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/appium-windows-driver

Authors and runs Appium 2.x tests against the Windows driver, the actively-maintained Node.js proxy in front of Microsoft's WinAppDriver: `appium driver install windows`, capabilities (`platformName: windows`, `appium:automationName: windows`, `appium:app`, `appium:appTopLevelWindow`, `appium:appArguments`), Windows gestures (`windows: scroll` / `clickAndDrag` / `keys`), PowerShell prerun/postrun hooks, and CI. Use when the stack already uses Appium for iOS / Android / Mac2 and Windows fits the existing client + capability model; to drive WinAppDriver directly from a Selenium-style client use winappdriver, and for a C#-only FlaUI client use flaui-tests.

74

Quality

93%

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

Overview
Quality
Evals
Security
Files

Quality

Content

85%

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 executable examples, an explicit validation checkpoint, and clean one-level-deep progressive disclosure. The main weakness is structural redundancy where the maintenance-gap narrative and install steps are repeated across sections.

Suggestions

State the WinAppDriver maintenance gap once (e.g. in Limitations) and reference it from Overview rather than re-explaining it in both places.

Consolidate installation into the 'Install' section and have 'How to use' step 1 link to it, instead of duplicating the install/pin commands in both.

Trim the Overview wrapper explanation that restates what the frontmatter description already covers.

DimensionReasoningScore

Conciseness

Mostly efficient and high-signal (tables, code, anti-patterns), but there is structural redundancy: the WinAppDriver maintenance gap is explained in both Overview and Limitations, the wrapper concept in Overview restates the description, and install steps appear in both 'How to use' step 1 and the 'Install' section.

2 / 3

Actionability

Provides copy-paste-ready executable material: install/pin commands, a capabilities table with example JSON, a complete Python worked example, and an anti-patterns table pairing each failure with a concrete fix.

3 / 3

Workflow Clarity

The 'How to use' section gives a clear 5-step sequence with an explicit validation checkpoint and feedback loop in step 1 ('Verify: `curl http://127.0.0.1:4723/status` returns HTTP 200 before proceeding; if it fails... re-check the launch and the driver install').

3 / 3

Progressive Disclosure

SKILL.md is a well-organized overview that pushes deep detail (gestures, multi-window, PowerShell hooks, CI) to a single one-level-deep, clearly signaled reference at references/gestures-hooks-and-ci.md, which exists and is itself well-sectioned without further nesting.

3 / 3

Total

11

/

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 strong, third-person description that states concrete capabilities, an explicit 'Use when' trigger, and clear sibling differentiation. It is comprehensive without padding and uses the vocabulary its target audience naturally employs.

DimensionReasoningScore

Specificity

Lists many concrete actions and artifacts: 'Authors and runs Appium 2.x tests', `appium driver install windows`, named capabilities (`platformName: windows`, `appium:app`, etc.), 'Windows gestures (`windows: scroll` / `clickAndDrag` / `keys`)', 'PowerShell prerun/postrun hooks, and CI' — comprehensive, not just a domain label.

3 / 3

Completeness

Answers both what ('Authors and runs Appium 2.x tests against the Windows driver...') and when with an explicit 'Use when the stack already uses Appium for iOS / Android / Mac2 and Windows fits the existing client + capability model' trigger clause.

3 / 3

Trigger Term Quality

Covers the natural terms a target user would actually say — 'Appium', 'Appium 2.x', 'Windows driver', 'WinAppDriver', 'PowerShell', 'CI', 'iOS / Android / Mac2' — which are the real vocabulary for this niche rather than generic jargon.

3 / 3

Distinctiveness Conflict Risk

Explicitly disambiguates siblings — 'to drive WinAppDriver directly from a Selenium-style client use winappdriver, and for a C#-only FlaUI client use flaui-tests' — giving a clear niche unlikely to trigger 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