Automation Flows

Windows Desktop Automation Architect

Designs reliable Windows desktop automations for legacy apps and GUIs with no API, combining UI Automation, hotkeys, image matching, and OCR with real failure handling.

Last updated Jul 11, 2026
FreeClaudeClaude CodeCursorGitHub Copilot
TL;DR

Windows Desktop Automation Architect is a free AI skill for automation flows. Designs reliable Windows desktop automations for legacy apps and GUIs with no API, combining UI Automation, hotkeys, image matching, and OCR with real failure handling. It works with Claude, Claude Code, Cursor and is ready to use out of the box.

Download Skill.md Package

About this skill

Most AI-generated desktop automation scripts break the first time a window resizes, a dialog appears a second late, or a button shifts three pixels. This skill turns Claude into a Windows automation architect that designs multi-layer selector strategies (UI Automation first, image matching second, OCR as a last resort), builds in retries, timeouts, and failure screenshots by default, and produces runnable pywinauto/pyautogui code plus a short design note explaining every fallback decision. It's built for legacy business software, Remote Desktop/Citrix sessions, report exports, repetitive data entry, and any Windows app that was never given a proper API.

What it does

Given a description of a repetitive Windows task (or a screenshot of the app), the skill produces a working automation plan and script: it picks the right selector strategy per UI element, sequences hotkeys and window waits correctly, adds OCR and image-matching fallbacks for elements UI Automation can't see, wraps every action in retry/timeout logic, and logs enough detail that a failure can be diagnosed without re-running the whole flow.

What is included

  • Full SKILL.md with the selector-strategy decision tree (UI Automation > image match > OCR)
  • Reference patterns for window waits, focus handling, and dialog interrupts
  • Retry, timeout, and failure-screenshot logging template
  • Guidance for Citrix/Remote Desktop sessions where accessibility trees are unreliable
  • Worked example: automating a data-entry task in a legacy Windows line-of-business app

How to use it

1. Download the windows-desktop-automation-architect-SKILL.md file
2. Drop it into your agent's skills folder (e.g. .claude/skills/ for Claude Code, or upload directly in a Claude.ai chat)
3. Describe the Windows task you want automated, ideally with a screenshot of the target app
4. Review the generated design note and script, then run it in a test environment before production use

Examples

Example input
I need to automate exporting a daily report from an internal Windows accounting app (no API) and saving it to a shared drive. The app is old, some dialogs pop up with a delay, and I'm running it over Remote Desktop.
Example output
Design note: using UI Automation as the primary selector layer since the app exposes standard Win32 controls; falling back to image matching for the custom-drawn export button UI Automation can't see; adding a 2-second dialog-wait loop before each click since RDP introduces latency; wrapping the save step in a 3-retry block with a screenshot-on-failure logger. Followed by a runnable pywinauto script implementing exactly that plan.

FAQ

What kinds of Windows apps does this work with?
Legacy line-of-business software, internal tools without APIs, and anything you'd normally have to click through manually — including apps running inside a Citrix or Remote Desktop session.
Do I need to already know pywinauto or UI Automation?
No. You describe the task in plain English, ideally with a screenshot, and the skill produces both the reasoning and the runnable script.
What happens when the accessibility tree is empty, like over Remote Desktop?
The skill falls back to image matching and, if needed, OCR, and says explicitly in the design note why it chose that fallback instead of silently guessing.
How is this different from just asking Claude to "write me a pyautogui script"?
A raw pyautogui script has no retry logic, no timeouts, and no fallback when a click misses. This skill treats those as required parts of the design, not afterthoughts, and explains its selector choice for every step.
Can it handle dialogs that pop up unpredictably, like save prompts or license warnings?
Yes — the skill builds in wait-and-check loops for expected interrupts and a documented pattern for handling unexpected ones without crashing the whole flow.
Does it work for one-off scripts or only long-running production automations?
Both. For a one-off task it still adds basic retries and logging so a failure is diagnosable; for production automations it adds the fuller failure-handling and logging pattern.

Related Skills

Automation FlowsFree

Automation Flow Reliability Designer

Design reliable business automations with triggers, conditions, safeguards, retries, ownership, monitoring, and recovery procedures.

ClaudeChatGPTCursor
#workflow automation#process automation#reliability
Automation FlowsFree

Contract Renewal and Obligation Automation Designer

Design contract-renewal automations with obligation tracking, notice windows, ownership, approvals, reminders, exceptions, evidence, and escalation.

ClaudeChatGPT
#contract automation#renewal reminders#obligation tracking
Automation FlowsFree

Cross App Automation Workflow Designer

Design reliable cross-app automations with triggers, actions, conditions, data mapping, retries, approvals, and monitoring.

ClaudeChatGPT
#workflow automation#Zapier#Make