computer-use

Automates Windows desktop GUI interaction via screenshots, mouse, keyboard, and UI Automation.

1|Updated Apr 24, 2025
One-click install
npx skills add https://github.com/Kobayashi2003/EasyPwsh --skill computer-use-kobayashi2003
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: computer-use
Source: https://github.com/Kobayashi2003/EasyPwsh/tree/main/config/skills/computer-use
Command: npx skills add https://github.com/Kobayashi2003/EasyPwsh --skill computer-use-kobayashi2003

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Many desktop applications (IDEs like Cursor, native Win32 apps, Electron apps) expose no automation API, forcing agents and users to fall back on fragile manual clicking and typing. This Skill gives an agent eyes (screenshots with coordinate grids), a hand (mouse move/click/drag/scroll), a keyboard (CJK/emoji-safe typing, IME-aware key combos), and UI Automation probing to drive any Windows GUI reliably. ## Core Features & Use Cases - Vision & Precision Targeting: Capture full screens, windows, or 1:1 region crops with optional coordinate grid overlays, and get exact control rectangles via UI Automation (ui-find) without spending vision tokens. - Input Automation: Move, click, drag, and scroll the mouse; type text (CJK/emoji/multi-line safe via message or clipboard modes); send key combos atomically with IME detection and switching to avoid silent keystroke loss. - Window & Process Management: Enumerate all top-level windows by handle (multi-window, multi-monitor, negative coordinates supported), focus/maximize/move windows, and wait for windows or pixel stability instead of blind sleeps. - Batching: Run many steps in a single process to eliminate per-call startup cost. - Use Case: Automate a workflow in Cursor IDE — find its window, focus it, send ctrl+shift+p, type a command, verify the result via edit -Mode read, and screenshot the outcome, all in one batch call. ## Quick Start Ask the AI to use the computer-use skill to take a screenshot of the current screen with a coordinate grid, then click a specific button in the target application window.

Frequently Asked Questions about computer-use

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate a Windows desktop app that has no API?

Use the computer.ps1 dispatcher to combine screenshots for vision, UI Automation (ui-find) for exact control rectangles, and mouse/keyboard actions for input. Batch multiple steps into one process call to minimize startup overhead and agent round-trips.

How to click a precise button or splitter on Windows from a script?

First try ui-find to get the control's exact rect and ready-to-click center point at zero vision cost. For splitters, use cursor-type -Scan to probe a line and find the exact pixel range, then feed those coordinates to the click action.

Why do my keystrokes get swallowed when typing into a Chinese or Japanese IME?

A bare letter or digit sent while a CJK IME is in native mode opens a composition window that eats all subsequent keys. Switch to English mode with the ime action first, send the keys, then restore the original conversion mode.

Does this work with Electron apps like VS Code or Cursor?

Yes. UI Automation works on Chromium/Electron apps, though the accessibility tree builds lazily — run ui-find twice if the first call returns only unnamed containers. Typing uses clipboard mode, which works on Electron, WPF, and Qt.

Why does my click land a few pixels off target?

Clicks usually miss because coordinates were hand-converted from a downscaled screenshot, multiplying error by 1/scale. Use the map line printed by each screenshot, ui-find's Click coordinates, or re-shoot the area as a 1:1 region crop.

What are the limitations of screenshot-based desktop automation?

Screenshots cost roughly width times height divided by 750 tokens and never show the mouse cursor. Prefer zero-vision checks like edit -Mode read, pixel color sampling, or ui-find, and reserve screenshots for when you genuinely need to see the screen.