Omarchy Skill

Treat this skill as an Omarchy operating mode, not just a command catalog. When working on an Omarchy system, prefer Omarchy-native wrappers and workflows over generic Linux one-liners that may bypass expected state handling. Use local script docs and names to choose the correct path. Each script has documentation at the top describing its purpose. DO NOT RUN A SCRIPT UNTIL YOU ARE SURE OF ITS PURPOSE.

Operating rules

Start with command name matching and in-file comments under /home/achals/.local/share/omarchy/bin.
Prefer read-only/status commands first (*list*, *status*, *current*, *available*, *version*).
Ask before broad or high-impact actions (*install*, *remove*, *reinstall*, *update*, *pkg*, *setup*, *set*).
Avoid bulk discovery execution. Do static inspection first.
Never assume omarchy-* scripts support standard CLI flags or parameters (including --help). Treat each script as custom; inspect its file/header comments first.

Worked examples (good vs bad)

Use these patterns whenever you operate on Omarchy. The goal is not "run an omarchy command at all costs"; the goal is to avoid bypassing Omarchy’s intended state-management flows.

1) Restarting Waybar

User intent: "Waybar is broken, restart it."