CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ui-tests-migration

Create, migrate, and stabilize PowerToys UI tests with Microsoft.PowerToys.UITest.Next and winappcli, through local VM success, commit/push, and CI validation. Use for ports, new UITest projects, flaky CI tests, persistent Hyper-V validation, Settings IPC authentication/test signing, Explorer/Shell selection, preview handlers, thumbnail providers, hotkey activation, stateful process lifecycle, composed WinUI/WebView visual baselines, or foreground failures. Covers APIs, scaffolding, test design, diagnostics, and the required handoff to ui-tests-pipeline-ci. Keywords: UI test, UITests, UITestAutomation.Next, winappcli, WinAppDriver, Selenium, Settings IPC, not-microsoft-signed, Authenticode, local VM, Hyper-V, checkpoint, migrate, flaky, CI stability, Explorer, Shell extension, WebView2.

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

An exemplary operational skill: fully executable commands, a validated multi-step workflow with explicit checkpoints and failure handling, and a well-structured one-level reference bundle. The residual issues are verbosity from repeated justifications and anecdotes, a dangling templates/ directory reference, and one second-level nested reference file.

Suggestions

Consolidate the Settings-IPC companion-signing guidance and the "one CI iteration instead of six" rationale into a single location (ci-stability.md) and reference it once, cutting the repetitions in the workflow, Build & validate, and What NOT to do sections.

Add the templates/ starter files (Module.UITests.Next.csproj, app.manifest, ModuleEndToEndTests.cs, TestHelper.cs) to the bundle, or fix the [templates/](templates/) and ../templates/* links in SKILL.md and project-setup.md to point at wherever they actually live.

Mention references/nuget-runtime-pack-cache.md directly in SKILL.md's required-reads or build section so it is not only discoverable through the second-level link inside project-setup.md.

DimensionReasoningScore

Conciseness

The body is dense with PowerToys-specific, hard-won knowledge Claude cannot infer (exact error codes NETSDK1004/MSB4803/0x800B0100, elevation semantics, DPI pitfalls) and offloads bulk detail to references, but it carries narrative padding and repetition: the "spend one CI iteration instead of six" point and the Settings-IPC companion-signing rule each appear three times, plus anecdotal asides like the "~8 iterations and a confident but entirely wrong product-defect report on File Locksmith". Not 3: nearly all content is domain-specific and instructional rather than explanation of known concepts; not 5: those anecdotes and duplicated points could be trimmed without losing guidance.

4 / 5

Actionability

Guidance is copy-paste executable throughout: exact build commands ("tools\build\build.cmd -Path src\modules\<Module>\Tests\<Module>.UITests.Next -Platform x64 -Configuration Debug"), the produced-exe run invocation with --filter/--report-trx flags, the csproj import requirement, the pipeline template path "$requiresAuthenticatedSettingsIpc ... .pipelines/v2/templates/job-test-project.yml", and a naming decision table with triggers. This matches anchor 5: specific commands cover the common cases with no gaps.

5 / 5

Workflow Clarity

The 14-step TODO workflow is explicitly ordered, each step linked to the reference that drives it, with validation checkpoints at every phase (build to exit code 0, run one deterministic test and diagnose the first failure, rerun-then-widen, full-matrix counts/payload hashes/evidence, record the exact SHA, synchronous CI wait within the three-run ceiling ending only on verified terminal success or an explicit blocker). Failure paths are also specified ("If the local VM is unavailable... report the exact environmental blocker; do not silently stop at compile validation"), matching anchor 5's feedback loops and checklists.

5 / 5

Progressive Disclosure

Structure is good: SKILL.md is an overview with an annotated, ordered "Required reads" list, and all 7 references it links (framework-differences, api-mapping, project-setup, porting-workflow, patterns-and-pitfalls, explorer-shell-tests, ci-stability) exist and are one level deep. Two minor gaps keep it from 5: references/nuget-runtime-pack-cache.md is reachable only through project-setup.md (a second nesting level), and the [templates/](templates/) links in SKILL.md and ../templates/* links in project-setup.md point at a templates/ directory that does not exist in the bundle. Not 3: content is appropriately split with clearly signaled navigation, not inlined.

4 / 5

Total

18

/

20

Passed

Description

96%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 strong description: third-person, concrete, lifecycle-complete, with an explicit and extensive trigger enumeration plus a keyword list covering both legacy and new harness vocabulary. The only weakness is that its local-VM/CI-stability keywords overlap closely with its sibling pipeline and local-VM skills.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete actions — "Create, migrate, and stabilize PowerToys UI tests", carried "through local VM success, commit/push, and CI validation" — and additionally scopes coverage ("APIs, scaffolding, test design, diagnostics"). Coverage is comprehensive with no generic filler; anchor 5 fits better than 4 because the actions span the full lifecycle, not just several.

5 / 5

Completeness

Both questions are answered explicitly: the "what" opens the description ("Create, migrate, and stabilize PowerToys UI tests with Microsoft.PowerToys.UITest.Next and winappcli...") and the "when" is a concrete "Use for..." clause enumerating ports, new UITest projects, flaky CI tests, Hyper-V validation, Settings IPC, Explorer/Shell, preview handlers, hotkey activation, and foreground failures. This matches anchor 5's requirement of concrete trigger phrases for both.

5 / 5

Trigger Term Quality

The explicit keyword list ("UI test, UITests, UITestAutomation.Next, winappcli, WinAppDriver, Selenium, Settings IPC, ... migrate, flaky, CI stability, Explorer, Shell extension, WebView2") covers natural phrasings and synonyms a user would actually say, including both legacy and new harness names and error-message terms like "not-microsoft-signed". Not score 4: the list includes synonym pairs (UI test/UITests, local VM/Hyper-V/checkpoint) that close the gaps anchor 4 allows.

5 / 5

Distinctiveness Conflict Risk

The PowerToys/.Next/winappcli framing gives it a clear niche that would not fire for unrelated skills, but several keywords ("local VM, Hyper-V, checkpoint, migrate, flaky, CI stability") overlap the sibling ui-tests-local-vm and ui-tests-pipeline-ci skills, creating minor mis-trigger risk within its own family. Not 5: those shared trigger terms mean a Hyper-V-checkpoint-only request could plausibly select this skill instead of the local-VM one; not 3: the overlap is confined to closely related siblings, not broad categories.

4 / 5

Total

19

/

20

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 missing, 10 suspicious

Warning

Total

15

/

16

Passed

Repository

microsoft/PowerToys

Path

.github/skills/ui-tests-migration/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.