Enforce Native Wayland and User-Owned Keybindings in Agent GUIs

Where this fits

A developer asks their agent to add a keyboard shortcut to a GUI tool. The agent proposes a Super-key chord and tells the user to disable their compositor's global binding. On Omarchy (Hyprland), that is a defect. This skill activates when shortcuts, Wayland, HiDPI, window rules, or any graphical tool is involved, and pulls in a desktop contract that keeps agent suggestions aligned with modern Linux desktop expectations.

Why agents benefit

• Recognizes GUI-related requests that generic agent skills might miss, such as "add a shortcut" or "make this tool HiDPI-aware".
• Blocks harmful defaults: no Super key unless the user explicitly rebinds it, no X11-only paths, no compositor workarounds.
• Enforces user-editable configuration files. The agent will propose a small text or JSON config, not a closed keymap.
• Points to the exact contract and existing display notes in the LET catalog, so agents have both normative and reference material.
• Handles the full desktop surface: window rules, Wayland support, HiDPI scaling, and graphical tool integration.

Practical scenarios

Adding a Super-key binding

The user wants a global shortcut for their app. The agent loads the skill and checks the default binding style. It suggests Ctrl+Alt+T instead of Super+T, and creates a user-editable shortcuts.json where the user can later map Super if they want.

Implementing Wayland support

A developer says "my tool currently uses X11, make it work on Wayland." The skill flags the current architecture as a defect under the desktop contract. The agent then plans a native Wayland path, using xdg-desktop-portal or layer-shell as appropriate, rather than telling the user to switch to X11.

Handling window rules

The user needs their app to match Omarchy's Hyprland behavior. The agent inspects ~/.config/hypr/bindings.lua as an example of style, then generates window rule snippets that respect the user's existing setup without overriding it.

Add it to your agent workflow

Install it in a terminal:

npx skills add linux-engineering-tools/community --skill omarchy-desktop

Once installed, the skill is triggered automatically when the agent sees relevant keywords. For example, when a user writes "Add a keyboard shortcut to launch my app," the agent will load the skill, recognize that Super is off-limits by default, and generate a user-editable config file with Ctrl-based defaults.

Compare before adopting

Before adopting, compare the skill with alternatives on a few dimensions. Look at quality signals: does it refer to a real spec and issue labels, or is it just marketing? Check maintenance freshness: recent commits and active issue responses. Note that the skill has 11 stars—low but expected for a niche system engineering tool. More important is whether it fits your workflow: if your agents rarely touch GUI or Linux desktop configuration, the skill may add noise. If they do, this contract prevents costly mistakes.

Why it is worth tracking

The skill is part of the linux-engineering-tools community, which tracks real desktop contracts rather than generic best practices. Its low star count is offset by the concrete, testable rules it encodes. The author actively links the skill to a spec and catalog, making it easier to audit. Track it when you need agents to behave correctly on Wayland desktops, and evaluate it again if the project gains traction. For a deeper look, see the skill listing at https://www.openagentskill.com/skills/linux-engineering-tools-omarchy-desktop.