omarchy

Contributors

GitHub-linked commit authors for this SKILL.md at the saved revision. Co-authors and history before file renames are not included.

File history ↗

REQUIRED for end-user customization of Linux desktop, window manager, or system config. Use when editing ~/.config/hypr/, ~/.config/omarchy/, ~/.config/alacritty/, ~/.config/foot/, ~/.config/kitty/, or ~/.config/ghostty/. Triggers: Hyprland, window rules, animations, keybindings, monitors, gaps, borders, blur, opacity, omarchy-shell, bar, terminal config, themes, background, night light, idle, lock screen, screenshots, reminders, layer rules, workspace settings, display config, and user-facing omarchy commands. Excludes Omarchy source development through `omarchy dev link` workflows.

default/agents/skills/omarchy/SKILL.md

Download bundle ↓
quattro · 86a2e587 bundle filesScanned 2026-09-14

hooks.md

267 tokens · o200k_base · 1,063 bytes

Source excerpt starting at line 1.
# Automation Hooks Read this before setting up scripts that run on system events (theme changes,updates, boot, low battery, etc.). Hooks live in `~/.config/omarchy/hooks/<name>.d/` — one directory per event,holding any number of independent scripts. Install with`omarchy hook install <name> <script>` (copies the script in and makes itexecutable). The runner also executes a flat `~/.config/omarchy/hooks/<name>`file first, if one exists. ```~/.config/omarchy/hooks/├── battery-low.d/          # Low battery (percentage in $1)├── font-set.d/             # After font change (font name in $1)├── post-boot.d/            # After the desktop starts├── post-update.d/          # During `omarchy update`, after system packages and migrations├── pre-refresh-pacman.d/   # Before `omarchy refresh pacman` re-syncs packages└── theme-set.d/            # After theme change (theme slug in $1)``` Example hook script:```bash#!/bin/bashTHEME_NAME=$1echo "Theme changed to: $THEME_NAME"# Add custom actions here``` 
Referenced from SKILL.md