Mirroir Onboard
jfarcand/mirroir-mcp
Onboard a consumer web app to mirroir's .mirroir/ dotfile by EXPLORING the running app (chrome-devtools-mcp) — derive real selectors from the accessibility tree, exercise each surface's primary…
A skill your agent uses when testing Windows 11 desktop apps (WinForms/WPF/UWP) via UFO UIA/Win32 automation MCP.
Install Windows QA Engineer
$ npx skills add CodeAlive-AI/ai-driven-development --skill windows-qa-engineer -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install CodeAlive-AI/ai-driven-development windows-qa-engineer --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/CodeAlive-AI/ai-driven-development.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/windows-qa-engineer .claude/skills/windows-qa-engineer && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "windows-qa-engineer" agent skill from https://github.com/CodeAlive-AI/ai-driven-development/tree/main/skills/windows-qa-engineer into .claude/skills/windows-qa-engineer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "windows-qa-engineer", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/CodeAlive-AI/ai-driven-development/tree/main/skills/windows-qa-engineerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add CodeAlive-AI/ai-driven-development --skill windows-qa-engineer -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install CodeAlive-AI/ai-driven-development windows-qa-engineer --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/CodeAlive-AI/ai-driven-development.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/windows-qa-engineer .agents/skills/windows-qa-engineer && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "windows-qa-engineer" agent skill from https://github.com/CodeAlive-AI/ai-driven-development/tree/main/skills/windows-qa-engineer into .agents/skills/windows-qa-engineer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "windows-qa-engineer", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add CodeAlive-AI/ai-driven-development --skill windows-qa-engineer -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install CodeAlive-AI/ai-driven-development windows-qa-engineer --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/CodeAlive-AI/ai-driven-development.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/windows-qa-engineer .cursor/skills/windows-qa-engineer && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "windows-qa-engineer" agent skill from https://github.com/CodeAlive-AI/ai-driven-development/tree/main/skills/windows-qa-engineer into .cursor/skills/windows-qa-engineer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "windows-qa-engineer", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/CodeAlive-AI/ai-driven-development.git --path skills/windows-qa-engineer--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add CodeAlive-AI/ai-driven-development --skill windows-qa-engineer -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install CodeAlive-AI/ai-driven-development windows-qa-engineer --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/CodeAlive-AI/ai-driven-development.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/windows-qa-engineer .gemini/skills/windows-qa-engineer && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "windows-qa-engineer" agent skill from https://github.com/CodeAlive-AI/ai-driven-development/tree/main/skills/windows-qa-engineer into .gemini/skills/windows-qa-engineer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "windows-qa-engineer", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install CodeAlive-AI/ai-driven-development windows-qa-engineerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add CodeAlive-AI/ai-driven-development --skill windows-qa-engineer -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/CodeAlive-AI/ai-driven-development.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/windows-qa-engineer .github/skills/windows-qa-engineer && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "windows-qa-engineer" agent skill from https://github.com/CodeAlive-AI/ai-driven-development/tree/main/skills/windows-qa-engineer into .github/skills/windows-qa-engineer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "windows-qa-engineer", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add CodeAlive-AI/ai-driven-development --skill windows-qa-engineer -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install CodeAlive-AI/ai-driven-development windows-qa-engineer --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/CodeAlive-AI/ai-driven-development.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/windows-qa-engineer .opencode/skills/windows-qa-engineer && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "windows-qa-engineer" agent skill from https://github.com/CodeAlive-AI/ai-driven-development/tree/main/skills/windows-qa-engineer into .opencode/skills/windows-qa-engineer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "windows-qa-engineer", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
windows-qa-engineer- GitHub stars
- 155
- Token cost
- ~1.4k tokens
- SKILL.md length
- 517 words
- Files
- 10 (incl. scripts, references, assets)
- Skills in repo
- 22
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when testing Windows 11 desktop apps (WinForms/WPF/UWP) via UFO UIA/Win32 automation MCP.
- Works in 6 steps: Discover windows → Select window → Collect controls → …
- Testing Windows 11 desktop apps (WinForms/WPF/UWP) via UFO UIA/Win32 automation MCP
- SKILL.md covers Auto-Setup (when MCP tools are…, Mandatory Workflow, Tool Reference and Example: Login Smoke Test, plus 3 more sections
- Runs Python and PowerShell scripts from its folder; calls python
What it does
Windows QA Engineer is an agent skill from CodeAlive-AI/ai-driven-development. Use when testing Windows 11 desktop apps (WinForms/WPF/UWP) via UFO UIA/Win32 automation MCP. Triggers on "test this Windows app", "QA the app", "run smoke test", "click the button", "fill the form", "check the UI", "Windows automation", "UFO QA", "verify the dialog", or any Windows desktop UI testing task. Not for web/browser testing (use Playwright), mobile testing, or non-Windows platforms.
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 12 other files, including scripts, reference files and assets (for example `README.md`, `assets/test-case.md` and `install.yaml`).
It sits in Testing & QA, covering QA and bug reports, Browser testing and Desktop control. It works with Windows, Model Context Protocol and Playwright. The repository describes itself as: Practices, protocols, and skills for AI-driven software development. Skills and safety hooks for Claude Code, Codex, OpenCode, Cursor, Antigravity, and any agent supporting the… The licence is MIT.
When your agent uses it
- Testing Windows 11 desktop apps (WinForms/WPF/UWP) via UFO UIA/Win32 automation MCP
- Test this Windows app
- Click the button
- Windows automation
Example prompts
- “test this Windows app”
- “QA the app”
- “run smoke test”
- “/windows-qa-engineer”
Requirements
- Python 3
- PowerShell
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 25b7b1d. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 4 files in scripts/ (Python and PowerShell), which the agent can run.
Shell commands in SKILL.md call:
python
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Windows QA Engineer loads about 1.4k tokens when it runs, and up to ~2.6k if it reads all its reference files. Until then it costs about 104 tokens; SKILL.md has 517 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from CodeAlive-AI/ai-driven-development at commit 25b7b1d, republished under its MIT licence (© CodeAlive-AI). 517 words, ~1,420 tokens.
Download SKILL.mdSave it as
.claude/skills/windows-qa-engineer/SKILL.md (or your agent's skills folder). This skill also uses 9 other files; get the full folder from GitHub.- name
- windows-qa-engineer
- description
- Use when testing Windows 11 desktop apps (WinForms/WPF/UWP) via UFO UIA/Win32 automation MCP. Triggers on "test this Windows app", "QA the app", "run smoke test", "click the button", "fill the form", "check the UI", "Windows automation", "UFO QA", "verify the dialog", or any Windows desktop UI testing task. Not for web/browser testing (use Playwright), mobile testing, or non-Windows platforms.
- metadata.compatibility
- Windows 11 or Windows Server 2025 Desktop Experience, Python 3.10, UFO, fastmcp
Windows QA Engineer (UFO-powered)
You are an AI-QA operator on the same interactive Windows desktop as the SUT. All automation uses UFO's real MCP tools (UICollector, HostUIExecutor, AppUIExecutor) -- no mocks.
The agent, UFO MCP process, and SUT must run in the same logged-in interactive Windows desktop session. SSH, WinRM, CI services, and Session 0 are headless even when they can start the SUT process; use an interactive console, RDP session, or a secured virtual desktop. Never expose RDP publicly merely to satisfy this requirement.
Auto-Setup (when MCP tools are missing)
If UFO tools are NOT available as MCP tools, run setup before QA work:
- Run:
python "<skill-dir>/scripts/skill_installer.py" --project-dir "<project-root>" - Parse the JSON output — if
successis true, restart the MCP client - If failed, show the error and direct user to references/setup.md for manual install
Mandatory Workflow
Follow this sequence for every test run. Do not skip steps.
1. Discover windows
- Call
qa_refresh_and_list_windows() - Identify the SUT window by title hint from the user
2. Select window
- Call
select_application_window(id, name)(HostUIExecutor) - Call
capture_window_screenshot()(UICollector) -- baseline screenshot
3. Collect controls
- Call
qa_refresh_controls(field_list=["label","control_text","control_type","automation_id","control_rect"]) - Anchor on
id+control_text/automation_idwhen the returned tree is usable - If control collection returns an error or an empty tree for a large/legacy WinForms window, continue with screenshot inspection and coordinate actions; do not repeatedly force full UIA subtree scans
4. Interact
- Use
click_input(id, name),set_edit_text(id, name, text),keyboard_input(id, name, keys) - Coordinate actions only as last resort (document why)
- Re-collect controls after navigation or dialog open
5. Assert
- Read with
texts(id, name)and compare against expected - Prefer
qa_wait_for_text_contains(id, name, expected, timeout_s=10)over sleeps - Screenshot after each major checkpoint
6. Report
- Fill assets/test-case.md template
- Numbered execution log (step -> tool call -> result)
- Final PASS/FAIL with exact failing assertion if applicable
- Attach screenshot base64 strings from
capture_window_screenshot()
Show full SKILL.md (220 more words)Show less
Tool Reference
| Tool | Server | Purpose |
|---|---|---|
qa_refresh_and_list_windows | QA helper | Refresh + list all windows |
select_application_window | HostUIExecutor | Select SUT by id+name |
get_app_window_controls_info | UICollector | Raw control tree; use only when helper output is insufficient |
capture_window_screenshot | UICollector | Screenshot selected window |
click_input | AppUIExecutor | Click control by id+name |
set_edit_text | AppUIExecutor | Type into control |
keyboard_input | AppUIExecutor | Send keystrokes |
texts | AppUIExecutor | Read control text |
qa_wait_for_text_contains | QA helper | Poll until text matches |
qa_refresh_controls | QA helper | Re-collect control tree with fail-soft parsing |
Example: Login Smoke Test
User says: "Test the login flow on MyApp"
1. qa_refresh_and_list_windows() → find "MyApp - Login"
2. select_application_window(id="3", name="MyApp - Login")
3. capture_window_screenshot() → baseline
4. qa_refresh_controls(field_list=["label","control_text","control_type","automation_id","control_rect"])
→ find username (id=12), password (id=14), login button (id=16)
5. set_edit_text(id="12", name="Username", text="testuser")
6. set_edit_text(id="14", name="Password", text="pass123")
7. click_input(id="16", name="Login")
8. qa_wait_for_text_contains(id="20", name="WelcomeLabel", expected_substring="Welcome", timeout_s=10)
→ {"ok": true, "text": "Welcome, testuser"}
9. capture_window_screenshot() → post-login
10. Report: PASSError Handling
No windows found: Re-check the SUT is running. Call qa_refresh_and_list_windows() again. If still empty, ask the user to confirm the app is open.
Empty control tree: The window may not have finished loading. Wait 2-3 seconds, then qa_refresh_controls(field_list=[...]). If still empty, try CONTROL_BACKEND=win32 (see setup.md). For large or legacy WinForms apps, avoid repeated full UIA subtree scans and use screenshot plus targeted coordinates.
Control not clickable / action fails: Re-collect controls (the tree may have changed after navigation). If the control lacks a usable id, fall back to coordinate-based action and document why.
MCP tools not found: Run auto-setup first (see Auto-Setup above). If auto-setup fails, direct the user to references/setup.md and run doctor.ps1.
Detailed Workflows
See references/qa-workflows.md for more examples, locator strategy, and common patterns.
Setup
See references/setup.md for UFO installation, MCP configuration, and diagnostics.
© CodeAlive-AI, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 9 other files (scripts, references, assets) in skills/windows-qa-engineer of CodeAlive-AI/ai-driven-development.
- SKILL.md
- README.md
- assets/test-case.md
- install.yaml
- references/qa-workflows.md
- references/setup.md
- scripts/doctor.ps1
- scripts/interactive_smoke_test.py
- scripts/skill_installer.py
- scripts/ufo_windows_qa_mcp_server.py
Open the folder on GitHubat commit 25b7b1d
Compare with similar skills
Windows QA Engineer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Windows QA Engineer this skillCodeAlive-AI/ai-driven-development | 155 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Mirroir Onboardjfarcand/mirroir-mcp | 245 | — | ~4.4k | Automated safety check: Notes | Apache-2.0 | |
| Agentic Browser Testingpetrkindlmann/qa-skills | 163 | — | ~4.5k | Automated safety check: Pass | MIT | |
| Hands On Testktnyt/cclsp | 675 | — | ~1.7k | Automated safety check: Pass | MIT | |
| Glance TestDebugBase/glance | 156 | — | ~827 | Automated safety check: Pass | MIT | |
| QA TesterJocysCom/FocusLogger | 213 | — | ~12k | Automated safety check: Pass | GPL-3.0 |
Similar skills
Agentic Browser Testing
petrkindlmann/qa-skills
Goal-driven E2E testing where a browser agent (Playwright MCP / computer-use) reads a natural-language goal and explores the app via the accessibility tree to assert outcomes — no pre-written script.
Hands On Test
ktnyt/cclsp
Performs manual hands-on testing of a web application using playwright-cli.
Glance Test
DebugBase/glance
Run E2E browser tests on any web application using Glance MCP.
QA Tester
JocysCom/FocusLogger
Create and maintain automated tests in Microsoft-native/.NET projects with a minimal stack — MSTest runner, System.Windows.Automation for Windows desktop, Playwright for real browser smoke.
Playwright MCP Browser Control
Hainrixz/editor-pro-max
Drives a live browser through the Playwright MCP server to navigate, inspect, fill forms and screenshot pages, with snapshot-first habits and output-size care.
More from CodeAlive-AI/ai-driven-development
All 22 skills in this repoInvestigating Repository History
CodeAlive-AI/ai-driven-development
Investigate GitHub repository history before risky code changes using git blame/log, GitHub PRs, review comments, squash/rebase/cherry-pick/rename heuristics, and cited evidence.
Plugins Management
CodeAlive-AI/ai-driven-development
Create, publish, delete, and submit plugins for coding agents (Claude Code, OpenCode, Devin CLI/Desktop).
Semantic Scholar Deep
CodeAlive-AI/ai-driven-development
Deep research over the Semantic Scholar Graph API. An agent skill from CodeAlive-AI/ai-driven-development.
Agentic Readiness
CodeAlive-AI/ai-driven-development
Audit and improve repositories for reliable agentic work across Codex and Codex App, Claude Code, and OpenCode.
Hooks Management
CodeAlive-AI/ai-driven-development
Manage hooks and automation for coding agents (Claude Code, Codex CLI, OpenCode, Devin CLI/Desktop).
Fetch URL As Markdown
CodeAlive-AI/ai-driven-development
Fetch a web page (URL) and return clean Markdown via local trafilatura, with Exa MCP as a fallback for JS-rendered or anti-bot pages.
Related
Works with
Categories
Questions about Windows QA Engineer
What does Windows QA Engineer do?
A skill your agent uses when testing Windows 11 desktop apps (WinForms/WPF/UWP) via UFO UIA/Win32 automation MCP. Windows QA Engineer is an agent skill from CodeAlive-AI/ai-driven-development. Use when testing Windows 11 desktop apps (WinForms/WPF/UWP) via UFO UIA/Win32 automation MCP.
When should I use Windows QA Engineer?
Windows QA Engineer fits situations like: testing Windows 11 desktop apps (WinForms/WPF/UWP) via UFO UIA/Win32 automation MCP; test this Windows app; click the button; windows automation.
How do I install Windows QA Engineer in Claude Code?
Run `npx skills add CodeAlive-AI/ai-driven-development --skill windows-qa-engineer -a claude-code`. Or copy the skill folder (skills/windows-qa-engineer in CodeAlive-AI/ai-driven-development) into .claude/skills/windows-qa-engineer in your project. Claude Code loads it when a task matches its description.
How do I install Windows QA Engineer in Codex?
Run `npx skills add CodeAlive-AI/ai-driven-development --skill windows-qa-engineer -a codex`. Or copy the skill folder (skills/windows-qa-engineer in CodeAlive-AI/ai-driven-development) into .agents/skills/windows-qa-engineer in your project. Codex loads it when a task matches its description.
Can I use Windows QA Engineer in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add CodeAlive-AI/ai-driven-development --skill windows-qa-engineer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/windows-qa-engineer, .gemini/skills/windows-qa-engineer, .github/skills/windows-qa-engineer and .opencode/skills/windows-qa-engineer in your project.
What does Windows QA Engineer need to run?
Going by SKILL.md and its folder, Windows QA Engineer needs Python and PowerShell for the scripts in its folder and the command-line tools its instructions call (python). Our summary lists: Python 3; PowerShell.
Does Windows QA Engineer access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Windows QA Engineer safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Windows QA Engineer use?
Windows QA Engineer is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Windows QA Engineer use?
About 1.4k tokens (SKILL.md is roughly 5.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.2k tokens, read only when the agent opens those files.
What are the alternatives to Windows QA Engineer?
Skills that share tags, products or a category with Windows QA Engineer: Mirroir Onboard (jfarcand/mirroir-mcp, 245 stars), Agentic Browser Testing (petrkindlmann/qa-skills, 163 stars), Hands On Test (ktnyt/cclsp, 675 stars) and Glance Test (DebugBase/glance, 156 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Windows QA Engineer?
CodeAlive-AI (a GitHub organization) maintains it in CodeAlive-AI/ai-driven-development, which has 155 GitHub stars. The repository holds 22 skills in this directory. The repository was last updated on October 6, 2026.
Source: CodeAlive-AI/ai-driven-development on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.