← ClaudeAtlas

manage-windowslisted

Work on a Windows machine from an agent — script it in PowerShell without the traps that fail silently, reach the interface with input that actually arrives, and verify the target before anything is pressed. Covers the encoding rules that differ between PowerShell 5.1 and 7, JSON that truncates without an error, the input ladder for XAML and WinUI applications, window measurement and DPI, elevation, and where generated scripts belong. Ships a preflight check that must pass before a click or a keystroke is sent. Use when the user asks to change a Windows setting, run or script something on Windows, automate a Windows application, install or configure software, read or write the registry, or when an agent has to touch a Windows desktop at all.
ubik-dsh/deepseek-harness-skills · ★ 0 · AI & Automation · score 63
Install: claude install-skill ubik-dsh/deepseek-harness-skills
# Working on Windows Two things fail quietly on Windows and one of them is data. **`ConvertTo-Json` truncates.** Past depth 2 it stops, returns valid JSON, and exits 0. There is no warning and no error — the object simply arrives with its nested parts missing. Always `-Depth`. **PowerShell 5.1 corrupts text.** A bare `powershell.exe` call is 5.1, and 5.1 writes a byte-order mark and mangles anything outside ASCII when it round-trips a file. This is not a curiosity: in the repository this skill was written in, it produced a defect where a file beginning with a BOM became unreadable by the very tool meant to read it. Those two are worth the skill on their own. The rest is the order of operations that keeps an agent from pressing a button on the wrong screen. --- ## Step 0 — which channel, before any of this **This skill is the platform. The method is `learn-an-interface`.** If the question is *how do I reach this control*, stop and read that one; it holds the order of channels — a documented API first, then a CLI, then the file format, then UI Automation, then a macro, and pixels last — and the reason each rung is preferred. Reaching for the screen is the last resort, not the first, and most tasks described as "click this" are a command away from being a one-liner. Read on when the answer is Windows itself: the platform's traps, PowerShell as the substrate, or input that has to land on an application. ## Step 1 — PowerShell is the substrate, and it has traps Prefer Po