CtrlK
BlogDocsLog inGet started
Tessl Logo

ui-tests-migration

Migrate and stabilize PowerToys UI tests from WinAppDriver/Selenium to Microsoft.PowerToys.UITest.Next and winappcli. Use for ports, new UITest projects, flaky CI tests, persistent local-VM validation on Hyper-V, resettable clean-baseline runs, Settings IPC authentication/test signing, Explorer/Shell selection, preview handlers, thumbnail providers, hotkey activation, stateful process lifecycle, composed WinUI/WebView visual baselines, or cross-window/foreground failures. Covers APIs, scaffolding, test design, diagnostics, agentic execution, and CI hardening. 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.

75

Quality

94%

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.

The body is a strong, actionable migration guide with concrete commands, a well-sequenced validated workflow, and a clean progressive-disclosure structure pointing to real reference files. Its only weaknesses are some trimmable prose anecdotes and two minor reference-organization gaps (an orphaned bundle file and an absent templates/ path).

Suggestions

Link references/nuget-runtime-pack-cache.md from the body (e.g. add it to 'Required reads' or the build/validate section) so every bundle file is discoverable, or remove it if unused.

Resolve the dangling templates/ reference — either confirm templates/ ships with the bundle and note its path, or point project-setup.md readers at the concrete starter files that actually exist.

Tighten the two longest prose admonitions (the File Locksmith ~8-iteration anecdote and the elevated-legacy-launch paragraph) to their actionable conclusion without the narrative padding.

DimensionReasoningScore

Conciseness

Dense, high-signal operational content (exact pwsh commands, file paths, error codes MSB4803/0x800B0100/NETSDK1004) that assumes competence, but several prose admonitions — the File Locksmith ~8-iteration anecdote and the elevated-launch paragraph — could be trimmed, fitting anchor 4 rather than a fully lean 5.

4 / 5

Actionability

Provides copy-paste-ready commands for restore, build, and run with exact paths, platform/config flags, --filter/--report-trx syntax, and concrete error codes covering the common build/run cases — anchor 5.

5 / 5

Workflow Clarity

The 11-step TODO workflow is clearly sequenced with explicit validation checkpoints (exit-code-0 build gate, single-deterministic-test-then-widen), a write→build→run→diagnose→repeat feedback loop, and a CI pre-flight checklist — anchor 5; the destructive/batch no-validation cap does not apply because validation is thorough.

5 / 5

Progressive Disclosure

Clear overview with well-signaled one-level-deep references (7 confirmed real references/*.md, each described in 'Required reads (in order)'), but references/nuget-runtime-pack-cache.md exists in the bundle with no body pointer and templates/ is referenced (via project-setup) yet absent — minor organization gaps pulling it to anchor 4 rather than 5.

4 / 5

Total

18

/

20

Passed

Description

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

The description is exemplary: it explicitly states what the skill does and when to use it, lists comprehensive concrete actions, and provides a dedicated keywords block with natural trigger terms. It occupies a distinctive niche with negligible overlap risk.

DimensionReasoningScore

Specificity

Names many concrete actions — migrate/stabilize, port, scaffold new UITest projects, persistent local-VM validation on Hyper-V, Settings IPC signing, Explorer/Shell selection, preview handlers, thumbnail providers, hotkey activation, composed WinUI/WebView visual baselines — comprehensive coverage matching the anchor-5 example.

5 / 5

Completeness

Explicitly answers both what ('Migrate and stabilize PowerToys UI tests... Covers APIs, scaffolding, test design, diagnostics, agentic execution, and CI hardening') and when ('Use for ports, new UITest projects, flaky CI tests, persistent local-VM validation on Hyper-V...') with concrete trigger phrases — anchor 5.

5 / 5

Trigger Term Quality

The explicit 'Keywords:' block enumerates natural terms and synonyms a user would say (UI test, UITests, winappcli, WinAppDriver, Selenium, not-microsoft-signed, Authenticode, flaky, CI stability, Shell extension, WebView2), giving comprehensive coverage.

5 / 5

Distinctiveness Conflict Risk

Clearly bounded to PowerToys UI-test migration with named frameworks (UITest.Next/winappcli) and distinctive triggers (not-microsoft-signed, Authenticode, Shell extension, WebView2), giving a clear niche with minimal conflict risk.

5 / 5

Total

20

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 missing, 8 suspicious

Warning

Total

15

/

16

Passed

Repository
microsoft/PowerToys
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.