CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/flaui-tests

Authors and runs FlaUI-based Windows UI tests - the .NET-native wrapper around Microsoft UI Automation (UIA2 + UIA3). Covers the `FlaUI.Core` / `FlaUI.UIA2` / `FlaUI.UIA3` NuGet packages, `Application.Launch` / `Application.Attach` lifecycles, `ConditionFactory` + `FindFirstDescendant` locator patterns, `Retry` waits, and xUnit / NUnit / MSTest harness integration. Use when the test stack is C# / .NET-first and the team wants idiomatic in-process UIA calls rather than the HTTP/JSON wire protocol of `winappdriver` or the Appium proxy layer of `appium-windows-driver`.

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.

Actionable, well-structured content with executable code and a clean progressive-disclosure split into one reference file. The main weakness is conciseness — some UIA2/UIA3 and CI content is duplicated across the spine and reference, and a version date sits inline.

Suggestions

Consolidate UIA2-vs-UIA3 selection into one section; the Authoring table and the dedicated 'UIA2 vs UIA3 selection' section overlap and could be merged to trim the spine.

Move the full CI workflow fully into references/flaui-api.md and keep only a one-line pointer in the CI section, rather than restating windows-latest / Session-0 guidance in both places.

Relocate the version/date detail (v5.0.0 released February 2025) to a separate 'Versions / status' note or drop it inline to avoid time-sensitive clutter in the overview.

DimensionReasoningScore

Conciseness

Assumes Claude's intelligence (no UIA primers) and most detail earns its place, but the ~370-line body repeats UIA2/UIA3 selection in two sections and re-describes CI in both the spine and the reference, plus an inline version date (v5.0.0, Feb 2025) that the rubric flags as time-sensitive.

2 / 3

Actionability

Provides fully executable, copy-paste-ready C# (Application.Launch, FindFirstDescendant lambdas, Retry.WhileNull, xUnit fixtures, STA attributes) and concrete dotnet test commands, not pseudocode.

3 / 3

Workflow Clarity

The authoring-to-running flow is clearly sectioned and includes a verification/feedback checkpoint ('run the suite... If a test fails with NullReference or Retry timeout... fix... then re-run before adding more cases'), satisfying explicit-validation sequencing.

3 / 3

Progressive Disclosure

A concise spine with a single well-signaled one-level-deep reference (references/flaui-api.md, a real file) for alternate locator forms and the full CI workflow, and the reference links back to SKILL.md.

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 highly specific, well-triggered description that cleanly states both capability and use conditions while disambiguating from sibling skills. No meaningful weaknesses under the description rubric.

DimensionReasoningScore

Specificity

Lists multiple concrete actions and API surfaces (Application.Launch/Attach, ConditionFactory + FindFirstDescendant, Retry waits, xUnit/NUnit/MSTest integration), matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly answers what ('Authors and runs FlaUI-based Windows UI tests...') and when via an explicit 'Use when...' clause, satisfying the both-what-and-when anchor.

3 / 3

Trigger Term Quality

Uses natural terms a user would say ('Windows UI tests', 'C# / .NET-first', 'WPF/WinForms') and surfaces the sibling alternatives winappdriver and appium-windows-driver as natural differentiating triggers.

3 / 3

Distinctiveness Conflict Risk

The .NET-native in-process UIA niche is clearly carved out and explicitly disambiguated from winappdriver and appium-windows-driver, making wrong-skill triggering unlikely.

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