Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Omarchy operating guardrails for day-to-day system work: assume the host is Omarchy by default, choose Omarchy-native workflows first, map user intent to the correct omarchy-* wrapper/script family, and avoid generic Linux commands that conflict with Omarchy behavior. Use whenever handling local system tasks on this host unless the user explicitly says it is not Omarchy; prioritize safe Omarchy commands, prevent non-Omarchy shortcuts (e.g., ad-hoc process killing/relaunch patterns), troubleshoot desktop behavior, and validate the right script before execution.
Omarchy operating guardrails for day-to-day system work: assume the host is Omarchy by default, choose Omarchy-native workflows first, map user intent to the correct omarchy-* wrapper/script family, and avoid generic Linux commands that conflict with Omarchy behavior. Use whenever handling local system tasks on this host unless the user explicitly says it is not Omarchy; prioritize safe Omarchy commands, prevent non-Omarchy shortcuts (e.g., ad-hoc process killing/relaunch patterns), troubleshoot desktop behavior, and validate the right script before execution.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
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.
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.
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.
User intent: "Waybar is broken, restart it." Bad (generic shortcut): pkill waybar && waybar Good (Omarchy-native): omarchy-restart-waybar Why: Omarchy wrappers usually handle environment/session assumptions better than raw kill-and-relaunch one-liners.
User intent: "I changed config, apply it." Bad: restarting random processes manually until things look fixed Good: use targeted refresh script first, e.g. omarchy-refresh-waybar, omarchy-refresh-hyprland, omarchy-refresh-config (pick by component) Why: refresh scripts are explicit and reversible; manual shotgun restarts are noisy and risky.
User intent: "Install/remove package X." Bad: using raw pacman/yay first without checking Omarchy wrappers Good: inspect and prefer omarchy-pkg-* flow (...-present, ...-missing, then ...-install/...-remove) Why: wrapper flow keeps behavior consistent with Omarchy expectations.
User intent: "Switch theme / sync theme to apps." Bad: editing dotfiles manually first and restarting random apps Good: omarchy-theme-list -> omarchy-theme-set -> app-specific follow-ups if needed (omarchy-theme-set-vscode, ...-browser, ...-obsidian) Why: Omarchy theme pipeline may include extra integration steps beyond plain config edits.
User intent: "Audio/Bluetooth/WiโFi stopped behaving." Bad: broad process killing (killall pipewire, random daemon restarts) Good: use targeted wrapper restarts such as omarchy-restart-pipewire, omarchy-restart-bluetooth, omarchy-restart-wifi Why: targeted wrappers reduce collateral damage and match Omarchyโs service model.
User intent: ambiguous request like "fix my display stack". Bad: execute many commands to discover options (for c in omarchy-*; do $c --help; done) Good: Statically inspect names in /home/achals/.local/share/omarchy/bin Read top-of-file script comments for likely candidates Start with read-only/status scripts Propose 1-3 likely commands and ask before high-impact actions Why: static inspection is safer, faster, and follows no-bulk-probing policy.
User intent: "Update system." Bad: directly running full update steps without checking availability/state Good: check first: omarchy-update-available (and related status) then execute appropriate Omarchy update path with confirmation for impactful steps Why: staged update flow reduces surprise breakage.
For any Omarchy task, follow this mini-checklist: Identify component (UI, package, theme, network, update, device, etc.) Find matching omarchy-* family by name and script header comments Prefer read-only/status command first Use targeted omarchy-refresh-*/omarchy-restart-* over raw kill/relaunch Ask before high-impact actions (install/remove/reinstall/update/setup/set)
Total commands: 161
omarchy-battery-monitor omarchy-battery-remaining
omarchy-branch-set
omarchy-channel-set
omarchy-cmd-apple-display-brightness omarchy-cmd-audio-switch omarchy-cmd-first-run omarchy-cmd-missing omarchy-cmd-present omarchy-cmd-reboot omarchy-cmd-screenrecord omarchy-cmd-screensaver omarchy-cmd-screenshot omarchy-cmd-share omarchy-cmd-shutdown omarchy-cmd-terminal-cwd
omarchy-debug
omarchy-dev-add-migration
omarchy-drive-info omarchy-drive-select omarchy-drive-set-password
omarchy-font-current omarchy-font-list omarchy-font-set
omarchy-hibernation-available omarchy-hibernation-remove omarchy-hibernation-setup
omarchy-hook
omarchy-hyprland-window-close-all omarchy-hyprland-window-pop omarchy-hyprland-workspace-toggle-gaps
omarchy-install-chromium-google-account omarchy-install-dev-env omarchy-install-docker-dbs omarchy-install-dropbox omarchy-install-steam omarchy-install-tailscale omarchy-install-terminal omarchy-install-vscode omarchy-install-xbox-controllers
omarchy-launch-about omarchy-launch-audio omarchy-launch-bluetooth omarchy-launch-browser omarchy-launch-editor omarchy-launch-floating-terminal-with-presentation omarchy-launch-or-focus omarchy-launch-or-focus-tui omarchy-launch-or-focus-webapp omarchy-launch-screensaver omarchy-launch-tui omarchy-launch-walker omarchy-launch-webapp omarchy-launch-wifi
omarchy-lock-screen
omarchy-menu omarchy-menu-keybindings
omarchy-migrate
omarchy-notification-dismiss
omarchy-pkg-add omarchy-pkg-aur-accessible omarchy-pkg-aur-add omarchy-pkg-aur-install omarchy-pkg-drop omarchy-pkg-install omarchy-pkg-missing omarchy-pkg-present omarchy-pkg-remove
omarchy-powerprofiles-list
omarchy-refresh-applications omarchy-refresh-chromium omarchy-refresh-config omarchy-refresh-fastfetch omarchy-refresh-hypridle omarchy-refresh-hyprland omarchy-refresh-hyprlock omarchy-refresh-hyprsunset omarchy-refresh-limine omarchy-refresh-pacman omarchy-refresh-plymouth omarchy-refresh-swayosd omarchy-refresh-walker omarchy-refresh-waybar
omarchy-reinstall omarchy-reinstall-configs omarchy-reinstall-git omarchy-reinstall-pkgs
omarchy-remove-dev-env
omarchy-reset-sudo
omarchy-restart-app omarchy-restart-bluetooth omarchy-restart-btop omarchy-restart-hyprctl omarchy-restart-hypridle omarchy-restart-hyprsunset omarchy-restart-mako omarchy-restart-opencode omarchy-restart-pipewire omarchy-restart-swayosd omarchy-restart-terminal omarchy-restart-walker omarchy-restart-waybar omarchy-restart-wifi omarchy-restart-xcompose
omarchy-setup-dns omarchy-setup-fido2 omarchy-setup-fingerprint
omarchy-show-done omarchy-show-logo
omarchy-snapshot
omarchy-state
omarchy-theme-bg-install omarchy-theme-bg-next omarchy-theme-current omarchy-theme-install omarchy-theme-list omarchy-theme-remove omarchy-theme-set omarchy-theme-set-browser omarchy-theme-set-gnome omarchy-theme-set-obsidian omarchy-theme-set-templates omarchy-theme-set-vscode omarchy-theme-update
omarchy-toggle-idle omarchy-toggle-nightlight omarchy-toggle-screensaver omarchy-toggle-suspend omarchy-toggle-waybar
omarchy-tui-install omarchy-tui-remove
omarchy-tz-select
omarchy-update omarchy-update-analyze-logs omarchy-update-available omarchy-update-available-reset omarchy-update-branch omarchy-update-confirm omarchy-update-firmware omarchy-update-git omarchy-update-keyring omarchy-update-perform omarchy-update-restart omarchy-update-system-pkgs omarchy-update-time omarchy-update-without-idle
omarchy-upload-log
omarchy-version omarchy-version-branch omarchy-version-channel omarchy-version-pkgs
omarchy-voxtype-config omarchy-voxtype-install omarchy-voxtype-model omarchy-voxtype-remove omarchy-voxtype-status
omarchy-webapp-handler-hey omarchy-webapp-handler-zoom omarchy-webapp-install omarchy-webapp-remove
omarchy-windows-vm
Identity, auth, scanning, governance, audit, and operational guardrails.
Largest current source with strong distribution and engagement signals.