skills.rest
nedos
nedosCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

winuse

Control Windows desktops via REST API for screenshots and input.

8|Updated Jan 31, 2026
Search Tags:#automation#screenshot#windows#keyboard#window-management#remote-control#mouse
One-click install
npx skills add https://github.com/nedos/winuse --skill winuse
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: winuse
Source: https://github.com/nedos/winuse/tree/main
Command: npx skills add https://github.com/nedos/winuse --skill winuse

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Many agents and automation scripts cannot directly interact with a Windows desktop; this Skill exposes a simple REST interface so tools can capture screens, send mouse and keyboard input, and manage windows without complex UI automation stacks.

Core Features & Use Cases

  • Screenshots: full-desktop and per-window captures served as files for vision models or verification.
  • Mouse control: absolute moves and single/double/right clicks for GUI interactions.
  • Keyboard input: clipboard-first paste, typed input, and press/key-combination endpoints for hotkeys.
  • Window management: enumerate windows, focus, minimize, maximize, and restore by HWND.
  • Use Case: run on a LAN Windows machine to let an agent open Notepad, paste text, click buttons, and confirm results via screenshots.

Quick Start

Point the agent at the WinUse server URL, take a screenshot, analyze it, and then send mouse or keyboard commands to act on the UI.

Frequently Asked Questions about winuse

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

FAQPage Schema
How do I automate mouse and keyboard input on a remote Windows desktop?▼

You can control a remote Windows desktop by pointing your agent at a REST API server that exposes endpoints for sending mouse clicks, keyboard inputs, and hotkeys to simulate GUI interactions over HTTP.

Can I capture screenshots of individual windows for vision models?▼

Yes, the REST API provides screenshot endpoints for both full-desktop and per-window captures, serving the images as files for immediate use by vision models or automated verification workflows.

Does Windows desktop automation over HTTP require a complex UI automation stack?▼

No, this approach replaces complex UI automation stacks with a simple REST interface, allowing tools to capture screens, manage windows, and send inputs directly, provided the server is running on the target Windows host.

How do I manage windows on a remote Windows machine via an API?▼

You can manage windows via REST API endpoints that allow you to enumerate open windows, then focus, minimize, maximize, and restore them by their HWND for precise GUI environment control during automation.

Can I use this for local automation or WSL scenarios?▼

Yes, this HTTP-based Windows desktop automation applies to LAN, WSL, and local automation scenarios, enabling agents to interact with the desktop environment wherever the server is running.

What is needed to run Windows desktop automation over HTTP?▼

You need a running WinUse server on the target Windows host; once active, agents can interact with endpoints for health checks, screenshots, mouse, keyboard, and window operations.

Related Skills

Explore More Software Engineering Skills→
nedosnedos
8

winuse-client

Control Windows desktops remotely via the WinUse HTTP API.

Community
Intermediate
Wike-CHIWike-CHI
2

desktop-control

Automate mouse, keyboard, and window operations with OpenCV-based image matching.

Community
Advanced
calcosmiccalcosmic
9

rest-api

Audit REST API design and documentation for consistent endpoints, schemas, and errors.

Community
Advanced
xianmingyaoxianmingyao
1

cli-anything-windows-control

Automate Windows UI interactions and control applications from the command line.

Community
Intermediate