Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Control and automate the Linux desktop GUI on X11. Use this skill to take screenshots, find and click UI elements, type text, send keyboard shortcuts, scroll...
Control and automate the Linux desktop GUI on X11. Use this skill to take screenshots, find and click UI elements, type text, send keyboard shortcuts, scroll...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Automate any X11 Linux desktop: capture screens, find and click elements, type, use hotkeys, manage windows. Preferred screenshot interpretation path: capture with capture.sh and interpret the image directly in your OpenClaw chat (existing image-capable model connection).
X11 session running (XFCE, GNOME on X11, KDE on X11, i3, openbox, etc.) DISPLAY environment variable set (usually :0) Run bash install.sh once to install dependencies No extra key needed for screenshot interpretation when using OpenClaw's image-capable chat path
TaskCommandTake screenshotbash capture.shScreenshot of windowbash capture.sh --window "Firefox"List windowsbash inspect.shActive window infobash inspect.sh --activeFind window by namebash inspect.sh --window "Firefox"Click at coordinatesbash click.sh --x 500 --y 300Right-clickbash click.sh --x 500 --y 300 --button rightDouble-clickbash click.sh --x 500 --y 300 --doubleClick relative to windowbash click.sh --window "Firefox" --x 200 --y 150Type textbash type.sh "hello world"Type into windowbash type.sh --window "Terminal" "ls -la"Send hotkeybash hotkey.sh "ctrl+c"Send Enterbash hotkey.sh "Return"Scroll downbash scroll.sh --direction down --amount 3Scroll up at positionbash scroll.sh --x 500 --y 300 --direction up --amount 3Focus windowbash window.sh --action focus --window "Firefox"Minimize windowbash window.sh --action minimize --window "Firefox"Maximize windowbash window.sh --action maximize --window "Firefox"Close windowbash window.sh --action close --window "Firefox"Move windowbash window.sh --action move --window "Firefox" --x 100 --y 50Resize windowbash window.sh --action resize --window "Firefox" --width 1280 --height 800
For most GUI automation tasks, follow this pattern: Capture a screenshot with capture.sh โ note the file path printed Look at the screenshot yourself to understand what's on screen Find the target element by examining the screenshot and estimating its pixel coordinates Act using the coordinates: click.sh --x X --y Y Verify by capturing another screenshot and checking the result
# Step 1: Capture the screen SCREENSHOT=$(bash capture.sh | tail -1) # Step 2: Look at the screenshot (read the image file with your vision) # Examine the image and identify the Save button's position # Step 3: Click at the coordinates you identified bash click.sh --x 450 --y 320
# Focus the terminal window and type a command bash type.sh --window "Terminal" "ls -la" bash hotkey.sh "Return"
# Maximize Firefox, then focus a terminal bash window.sh --action maximize --window "Firefox" bash window.sh --action focus --window "Terminal"
All tools support a --json flag for machine-readable output: {"success": true, "output": "...", "error": null} On failure: {"success": false, "output": null, "error": "Error description"}
If DISPLAY is not set (e.g., running over SSH), set it before calling any tool: export DISPLAY=:0 For headless servers with a virtual display: Xvfb :0 -screen 0 1920x1080x24 & export DISPLAY=:0
Key names follow X11 conventions: KeyNameEnterReturnTabTabEscapeEscapeBackspaceBackSpaceDeleteDeleteHomeHomeEndEndPage UpPage_UpPage DownPage_DownF1-F12F1 through F12Super/WinsuperCtrlctrlAltaltShiftshift Combine with +: ctrl+c, ctrl+shift+t, alt+F4, super+d
X11 only โ does not work on Wayland sessions Cannot interact with Wayland-native apps in a Wayland session Some apps with custom rendering (games, Electron apps with security flags) may resist automation Screenshot quality depends on compositor; disable compositing if captures look wrong
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.