omarchy

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.

This skill appears coherent: it guides the agent to prefer and inspect local omarchy-* wrapper scripts instead of running raw system commands, and it doesn't request credentials or install code. Before installing, confirm that this host actually uses Omarchy and that the hard-coded path (/home/achals/.local/share/omarchy/bin) matches your environment; otherwise the skill may attempt to read a different user's home-path or be ineffective. Also review the actual scripts in the referenced directory (and their header comments) so you trust what the agent may propose running, and be cautious about granting the agent autonomous execution rights if you do not want it to run local scripts without approval.

Type: OpenClaw Skill Name: omarchy Version: 0.1.1 The `SKILL.md` file exhibits strong prompt injection techniques designed to restrict the AI agent's autonomy and steer its behavior towards a predefined set of `omarchy-*` wrapper scripts. It explicitly instructs the agent to avoid generic Linux commands (e.g., `pacman`, `pkill`) and discourages standard inspection methods like `--help` flags, instead forcing reliance on internal documentation of the `omarchy-*` scripts. While not directly containing malicious code, this setup creates a highly vulnerable environment where the agent is compelled to use potentially unverified, controlled scripts for critical system operations (e.g., `omarchy-pkg-install`, `omarchy-update-system-pkgs`, `omarchy-reset-sudo`, `omarchy-upload-log`), increasing the risk of hidden malicious actions or system compromise if those underlying scripts were untrustworthy.