hyprland-control
Skill1 starsChanged 5 months agoMITView on GitHub
Inspect and control the Hyprland Wayland desktop from the shell via hyprctl — list/query windows, focus/move/resize/close them, switch and move things between workspaces, launch apps onto a target workspace, read monitor and cursor state. Use on Hyprland (Wayland) for any window or workspace management. Not for X11 (use wmctrl/xdotool there).
In this repository24 other files it gives its agents.
- api-designSkill
- brainstormingSkill
- councilSkill
- dispatching-parallel-agentsSkill
- document-toolkitSkill
- executing-plansSkill
- gui-input-automationSkill
- humanizeSkill
- incremental-implementationSkill
- issue-to-prSkill
- litreviewSkill
- mcp-builderSkill
- rust-reviewSkill
- screen-captureSkill
- session-handoffSkill
- shadcn-auditSkill
- spec-to-issuesSkill
- subagent-driven-developmentSkill
- teachSkill
- unslopSkill
- using-git-worktreesSkill
- visual-computer-use-loopSkill
- writing-flowSkill
- writing-plansSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Only works on Hyprland (echo $XDG_CURRENT_DESKTOP → Hyprland).
- Very specific: line 75
After launching, poll hyprctl clients -j for the new window's address before acting on it — it isn't there instantly.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Hyprland Control
Drive the Hyprland desktop with hyprctl. Everything is queryable as JSON (-j)
and pipeable through jq, and every action is a dispatch.
Only works on Hyprland (echo $XDG_CURRENT_DESKTOP → Hyprland). On X11 use
wmctrl/xdotool instead.
Query state (read-only, always safe)
hyprctl clients -j # all windows: class, title, address, at[x,y], size[w,h], workspace, pid
hyprctl activewindow -j # the focused window
hyprctl workspaces -j # all workspaces
hyprctl activeworkspace -j
hyprctl monitors -j # outputs: name, resolution, scale, position, focused
hyprctl cursorpos # "X, Y" in logical pixels
hyprctl devices -j # keyboards, miceUseful extractions:
# active window class + title
hyprctl activewindow -j | jq -r '.class + " — " + .title'
# find a window's address by class
hyprctl clients -j | jq -r '.[] | select(.class=="firefox") | .address'
# list "class | title | workspace" for every window
hyprctl clients -j | jq -r '.[] | "\(.class)\t\(.title)\tws\(.workspace.id)"'A window is targeted by a selector: address:0x… (most precise),
class:…, initialclass:…, title:…, initialtitle:…, or pid:….
Act (dispatch)
# focus
hyprctl dispatch focuswindow address:0x55feac7945f0
hyprctl dispatch focuswindow class:org.kde.konsole
hyprctl dispatch movefocus l # l/r/u/d — focus neighbour
# workspaces
hyprctl dispatch workspace 3 # switch to workspace 3
hyprctl dispatch movetoworkspace 3 # move active window to ws 3 (and follow)
hyprctl dispatch movetoworkspacesilent 3,address:0x… # move a specific window, don't follow
# move / resize the active (or addressed) window
hyprctl dispatch togglefloating # floating windows can be placed freely
hyprctl dispatch movewindowpixel "exact 100 100,address:0x…"
hyprctl dispatch resizewindowpixel "exact 1280 800,address:0x…"
hyprctl dispatch fullscreen 1 # 0=full, 1=maximize
hyprctl dispatch closewindow address:0x…
# cursor
hyprctl dispatch movecursor 960 540 # absolute, logical pixelsLaunch an app (optionally onto a workspace)
hyprctl dispatch exec firefox
# launch silently onto workspace 4 without switching to it:
hyprctl dispatch exec "[workspace 4 silent] firefox"
# launch floating, centered:
hyprctl dispatch exec "[float; center] kitty"After launching, poll hyprctl clients -j for the new window's address before
acting on it — it isn't there instantly.
Batch several actions
hyprctl --batch "dispatch workspace 2 ; dispatch exec kitty ; dispatch movecursor 100 100"Runtime config tweaks
hyprctl keyword general:gaps_out 5 # change a setting live (not persisted)
hyprctl reload # reload hyprland.confNotes & gotchas
- Coordinates are logical pixels. If a monitor has
scale ≠ 1(hyprctl monitors -j | jq '.[].scale'), logical ≠ physical — matters when pairing with screenshots (see the screen-capture and visual-computer-use-loop skills). - Multi-monitor: window
atis global across all outputs; account for monitorpositionoffsets. - Tiled windows ignore pixel moves/resizes —
togglefloatingfirst. - Confirm before
closewindowon anything with unsaved work.
Pairs with
- screen-capture — see what's on screen.
- gui-input-automation — click/type into the window you focused.
- clipboard-and-notifications —
notify-sendto report what you did.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

