linux-computer-use

Inspect Hyprland desktop state and interact with visible applications via CLI.

6|Updated Jul 9, 2019
One-click install
npx skills add https://github.com/sluongng/dotfiles --skill linux-computer-use
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: linux-computer-use
Source: https://github.com/sluongng/dotfiles/tree/main/config/claude/skills/linux-computer-use
Command: npx skills add https://github.com/sluongng/dotfiles --skill linux-computer-use

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reduces risk and complexity of manually probing and controlling visible desktop apps on Hyprland by providing a uniform, auditable interface.

Core Features & Use Cases

  • Live app state inspection with AT-SPI queries and screenshots.
  • Safe input handling with dry-run and explicit approvals for actions.
  • MCP-compatible tool calls enabling automation and integration.

Quick Start

Verify the CLI is installed and then run a basic Hyprland session inspection.

Frequently Asked Questions about linux-computer-use

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

FAQPage Schema
How do I automate Hyprland desktop apps using a CLI?

You can automate Hyprland desktop apps by using a local CLI to inspect live desktop state and safely interact with visible applications via MCP-compatible tool calls.

How does AT-SPI state querying work for Linux desktop automation?

AT-SPI state querying works by inspecting the live application state within your Hyprland session, allowing you to capture screenshots and query UI elements before executing actions.

Can I perform dry-run input handling for Linux desktop automation?

Yes, you can perform dry-run input handling to safely test interactions with visible applications, ensuring actions are auditable and require explicit approvals before execution.

Do I need a specific CLI installed to inspect Hyprland app states?

Yes, you need a functional linux-computer-use CLI or MCP server installed to operate within restricted environments and inspect Hyprland app states.

What is the best way to safely interact with visible applications on Hyprland?

The best way to safely interact with visible applications on Hyprland is by using a uniform, auditable interface that supports explicit approvals and dry-run mode for input handling.

Does this approach support MCP-compatible tool calls for desktop automation?

Yes, this approach supports MCP-compatible tool calls, enabling automation and integration while maintaining safety through dry-run modes and explicit action approvals.