omarchy_skill

Overview

This skill provides Omarchy operating guardrails for day-to-day system work on hosts that run the Omarchy environment. It enforces a workflow that prefers Omarchy-native wrappers and status commands, maps user intent to the correct omarchy-* script family, and prevents ad-hoc Linux shortcuts that can bypass Omarchy state handling. Use this skill as the default mode when performing local maintenance unless the user explicitly says the host is not Omarchy.

How this skill works

The skill inspects local omarchy-* scripts by name and header comments under /home/achals/.local/share/omarchy/bin to find the correct wrapper for a task. It recommends read-only/status commands first, suggests targeted refresh/restart wrappers instead of raw process kills, and prompts before any high-impact install/remove/update actions. It treats each script as custom (do not assume standard flags) and requires validating a script's purpose before execution.

When to use it

• When you are operating on the host that defaults to Omarchy behavior
• Before running any system, UI, or package command to avoid bypassing Omarchy state flows
• When troubleshooting desktop UI components like Waybar, Hyprland, or theme sync
• When performing package or update tasks so the Omarchy pkg/update flow is followed
• When intent is ambiguous and you need a safe discovery/check-first approach

Best practices

• Match command names and read top-of-file comments in /home/achals/.local/share/omarchy/bin before running a script
• Start with read-only/status scripts (list, status, current, available, version) to gather state
• Prefer targeted omarchy-refresh-* or omarchy-restart-* wrappers over kill/relaunch one-liners
• Ask for confirmation before high-impact actions: install, remove, reinstall, update, setup, set
• Avoid bulk probing (don’t run many scripts to discover behavior); perform static inspection first
• Never assume omarchy-* scripts accept standard CLI flags; inspect each script’s header

Example use cases

• Waybar is broken: recommend and run omarchy-restart-waybar rather than pkill and relaunch
• You changed config and need to apply it: run omarchy-refresh-config or component-specific refresh
• Install a package: inspect omarchy-pkg-present / omarchy-pkg-missing then follow omarchy-pkg-install flow
• Fix audio or Bluetooth: use omarchy-restart-pipewire or omarchy-restart-bluetooth instead of killing services
• System update: check omarchy-update-available and follow staged update commands with confirmation