[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75BPFQ0WS12W5AZR0R4VRW2":3,"skill-same:01M75BPFQ0WS12W5AZR0R4VRW2":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M75BPFQ0WS12W5AZR0R4VRW2","omarchy",null,"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\u002Fscript 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\u002Frelaunch patterns), troubleshoot desktop behavior, and validate the right script before execution.","javimosch\u002Fopen-claw-skills","javimosch","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F12900508?v=4","01M6D3F2AS6PV75ET9PZ1QGP8J","Javier Leandro Arancibia","01M75B8NCTAJG9WH5YNZH7C3D8",0,"MIT","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fachals-iglu\u002Fomarchy\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: omarchy\ndescription: \"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\u002Fscript 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\u002Frelaunch patterns), troubleshoot desktop behavior, and validate the right script before execution.\"\n---\n\n# Omarchy Skill\n\nTreat 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.\n\n## Operating rules\n\n1. Start with command name matching and in-file comments under `\u002Fhome\u002Fachals\u002F.local\u002Fshare\u002Fomarchy\u002Fbin`.\n2. Prefer read-only\u002Fstatus commands first (`*list*`, `*status*`, `*current*`, `*available*`, `*version*`).\n3. Ask before broad or high-impact actions (`*install*`, `*remove*`, `*reinstall*`, `*update*`, `*pkg*`, `*setup*`, `*set*`).\n4. Avoid bulk discovery execution. Do static inspection first.\n5. Never assume `omarchy-*` scripts support standard CLI flags or parameters (including `--help`). Treat each script as custom; inspect its file\u002Fheader comments first.\n\n## Worked examples (good vs bad)\n\nUse 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.\n\n### 1) Restarting Waybar\n\nUser intent: \"Waybar is broken, restart it.\"\n\n- Bad (generic shortcut):\n  - `pkill waybar && waybar`\n- Good (Omarchy-native):\n  - `omarchy-restart-waybar`\n- Why: Omarchy wrappers usually handle environment\u002Fsession assumptions better than raw kill-and-relaunch one-liners.\n\n### 2) Applying config\u002FUI refresh after edits\n\nUser intent: \"I changed config, apply it.\"\n\n- Bad:\n  - restarting random processes manually until things look fixed\n- Good:\n  - use targeted refresh script first, e.g. `omarchy-refresh-waybar`, `omarchy-refresh-hyprland`, `omarchy-refresh-config` (pick by component)\n- Why: refresh scripts are explicit and reversible; manual shotgun restarts are noisy and risky.\n\n### 3) Package management task\n\nUser intent: \"Install\u002Fremove package X.\"\n\n- Bad:\n  - using raw `pacman`\u002F`yay` first without checking Omarchy wrappers\n- Good:\n  - inspect and prefer `omarchy-pkg-*` flow (`...-present`, `...-missing`, then `...-install`\u002F`...-remove`)\n- Why: wrapper flow keeps behavior consistent with Omarchy expectations.\n\n### 4) Theme change request\n\nUser intent: \"Switch theme \u002F sync theme to apps.\"\n\n- Bad:\n  - editing dotfiles manually first and restarting random apps\n- Good:\n  - `omarchy-theme-list` -> `omarchy-theme-set` -> app-specific follow-ups if needed (`omarchy-theme-set-vscode`, `...-browser`, `...-obsidian`)\n- Why: Omarchy theme pipeline may include extra integration steps beyond plain config edits.\n\n### 5) Audio\u002FBluetooth\u002FWi‑Fi issue\n\nUser intent: \"Audio\u002FBluetooth\u002FWi‑Fi stopped behaving.\"\n\n- Bad:\n  - broad process killing (`killall pipewire`, random daemon restarts)\n- Good:\n  - use targeted wrapper restarts such as `omarchy-restart-pipewire`, `omarchy-restart-bluetooth`, `omarchy-restart-wifi`\n- Why: targeted wrappers reduce collateral damage and match Omarchy’s service model.\n\n### 6) \"What command should I run?\" discovery flow\n\nUser intent: ambiguous request like \"fix my display stack\".\n\n- Bad:\n  - execute many commands to discover options (`for c in omarchy-*; do $c --help; done`)\n- Good:\n  1. Statically inspect names in `\u002Fhome\u002Fachals\u002F.local\u002Fshare\u002Fomarchy\u002Fbin`\n  2. Read top-of-file script comments for likely candidates\n  3. Start with read-only\u002Fstatus scripts\n  4. Propose 1-3 likely commands and ask before high-impact actions\n- Why: static inspection is safer, faster, and follows no-bulk-probing policy.\n\n### 7) Update workflow\n\nUser intent: \"Update system.\"\n\n- Bad:\n  - directly running full update steps without checking availability\u002Fstate\n- Good:\n  - check first: `omarchy-update-available` (and related status)\n  - then execute appropriate Omarchy update path with confirmation for impactful steps\n- Why: staged update flow reduces surprise breakage.\n\n## Decision template (apply every time)\n\nFor any Omarchy task, follow this mini-checklist:\n\n1. Identify component (UI, package, theme, network, update, device, etc.)\n2. Find matching `omarchy-*` family by name and script header comments\n3. Prefer read-only\u002Fstatus command first\n4. Use targeted `omarchy-refresh-*`\u002F`omarchy-restart-*` over raw kill\u002Frelaunch\n5. Ask before high-impact actions (`install\u002Fremove\u002Freinstall\u002Fupdate\u002Fsetup\u002Fset`)\n\n## Omarchy command catalog (static, local)\n\nTotal commands: **161**\n\n### battery (2)\n- `omarchy-battery-monitor`\n- `omarchy-battery-remaining`\n\n### branch (1)\n- `omarchy-branch-set`\n\n### channel (1)\n- `omarchy-channel-set`\n\n### cmd (12)\n- `omarchy-cmd-apple-display-brightness`\n- `omarchy-cmd-audio-switch`\n- `omarchy-cmd-first-run`\n- `omarchy-cmd-missing`\n- `omarchy-cmd-present`\n- `omarchy-cmd-reboot`\n- `omarchy-cmd-screenrecord`\n- `omarchy-cmd-screensaver`\n- `omarchy-cmd-screenshot`\n- `omarchy-cmd-share`\n- `omarchy-cmd-shutdown`\n- `omarchy-cmd-terminal-cwd`\n\n### debug (1)\n- `omarchy-debug`\n\n### dev (1)\n- `omarchy-dev-add-migration`\n\n### drive (3)\n- `omarchy-drive-info`\n- `omarchy-drive-select`\n- `omarchy-drive-set-password`\n\n### font (3)\n- `omarchy-font-current`\n- `omarchy-font-list`\n- `omarchy-font-set`\n\n### hibernation (3)\n- `omarchy-hibernation-available`\n- `omarchy-hibernation-remove`\n- `omarchy-hibernation-setup`\n\n### hook (1)\n- `omarchy-hook`\n\n### hyprland (3)\n- `omarchy-hyprland-window-close-all`\n- `omarchy-hyprland-window-pop`\n- `omarchy-hyprland-workspace-toggle-gaps`\n\n### install (9)\n- `omarchy-install-chromium-google-account`\n- `omarchy-install-dev-env`\n- `omarchy-install-docker-dbs`\n- `omarchy-install-dropbox`\n- `omarchy-install-steam`\n- `omarchy-install-tailscale`\n- `omarchy-install-terminal`\n- `omarchy-install-vscode`\n- `omarchy-install-xbox-controllers`\n\n### launch (14)\n- `omarchy-launch-about`\n- `omarchy-launch-audio`\n- `omarchy-launch-bluetooth`\n- `omarchy-launch-browser`\n- `omarchy-launch-editor`\n- `omarchy-launch-floating-terminal-with-presentation`\n- `omarchy-launch-or-focus`\n- `omarchy-launch-or-focus-tui`\n- `omarchy-launch-or-focus-webapp`\n- `omarchy-launch-screensaver`\n- `omarchy-launch-tui`\n- `omarchy-launch-walker`\n- `omarchy-launch-webapp`\n- `omarchy-launch-wifi`\n\n### lock (1)\n- `omarchy-lock-screen`\n\n### menu (2)\n- `omarchy-menu`\n- `omarchy-menu-keybindings`\n\n### migrate (1)\n- `omarchy-migrate`\n\n### notification (1)\n- `omarchy-notification-dismiss`\n\n### pkg (9)\n- `omarchy-pkg-add`\n- `omarchy-pkg-aur-accessible`\n- `omarchy-pkg-aur-add`\n- `omarchy-pkg-aur-install`\n- `omarchy-pkg-drop`\n- `omarchy-pkg-install`\n- `omarchy-pkg-missing`\n- `omarchy-pkg-present`\n- `omarchy-pkg-remove`\n\n### powerprofiles (1)\n- `omarchy-powerprofiles-list`\n\n### refresh (14)\n- `omarchy-refresh-applications`\n- `omarchy-refresh-chromium`\n- `omarchy-refresh-config`\n- `omarchy-refresh-fastfetch`\n- `omarchy-refresh-hypridle`\n- `omarchy-refresh-hyprland`\n- `omarchy-refresh-hyprlock`\n- `omarchy-refresh-hyprsunset`\n- `omarchy-refresh-limine`\n- `omarchy-refresh-pacman`\n- `omarchy-refresh-plymouth`\n- `omarchy-refresh-swayosd`\n- `omarchy-refresh-walker`\n- `omarchy-refresh-waybar`\n\n### reinstall (4)\n- `omarchy-reinstall`\n- `omarchy-reinstall-configs`\n- `omarchy-reinstall-git`\n- `omarchy-reinstall-pkgs`\n\n### remove (1)\n- `omarchy-remove-dev-env`\n\n### reset (1)\n- `omarchy-reset-sudo`\n\n### restart (15)\n- `omarchy-restart-app`\n- `omarchy-restart-bluetooth`\n- `omarchy-restart-btop`\n- `omarchy-restart-hyprctl`\n- `omarchy-restart-hypridle`\n- `omarchy-restart-hyprsunset`\n- `omarchy-restart-mako`\n- `omarchy-restart-opencode`\n- `omarchy-restart-pipewire`\n- `omarchy-restart-swayosd`\n- `omarchy-restart-terminal`\n- `omarchy-restart-walker`\n- `omarchy-restart-waybar`\n- `omarchy-restart-wifi`\n- `omarchy-restart-xcompose`\n\n### setup (3)\n- `omarchy-setup-dns`\n- `omarchy-setup-fido2`\n- `omarchy-setup-fingerprint`\n\n### show (2)\n- `omarchy-show-done`\n- `omarchy-show-logo`\n\n### snapshot (1)\n- `omarchy-snapshot`\n\n### state (1)\n- `omarchy-state`\n\n### theme (13)\n- `omarchy-theme-bg-install`\n- `omarchy-theme-bg-next`\n- `omarchy-theme-current`\n- `omarchy-theme-install`\n- `omarchy-theme-list`\n- `omarchy-theme-remove`\n- `omarchy-theme-set`\n- `omarchy-theme-set-browser`\n- `omarchy-theme-set-gnome`\n- `omarchy-theme-set-obsidian`\n- `omarchy-theme-set-templates`\n- `omarchy-theme-set-vscode`\n- `omarchy-theme-update`\n\n### toggle (5)\n- `omarchy-toggle-idle`\n- `omarchy-toggle-nightlight`\n- `omarchy-toggle-screensaver`\n- `omarchy-toggle-suspend`\n- `omarchy-toggle-waybar`\n\n### tui (2)\n- `omarchy-tui-install`\n- `omarchy-tui-remove`\n\n### tz (1)\n- `omarchy-tz-select`\n\n### update (14)\n- `omarchy-update`\n- `omarchy-update-analyze-logs`\n- `omarchy-update-available`\n- `omarchy-update-available-reset`\n- `omarchy-update-branch`\n- `omarchy-update-confirm`\n- `omarchy-update-firmware`\n- `omarchy-update-git`\n- `omarchy-update-keyring`\n- `omarchy-update-perform`\n- `omarchy-update-restart`\n- `omarchy-update-system-pkgs`\n- `omarchy-update-time`\n- `omarchy-update-without-idle`\n\n### upload (1)\n- `omarchy-upload-log`\n\n### version (4)\n- `omarchy-version`\n- `omarchy-version-branch`\n- `omarchy-version-channel`\n- `omarchy-version-pkgs`\n\n### voxtype (5)\n- `omarchy-voxtype-config`\n- `omarchy-voxtype-install`\n- `omarchy-voxtype-model`\n- `omarchy-voxtype-remove`\n- `omarchy-voxtype-status`\n\n### webapp (4)\n- `omarchy-webapp-handler-hey`\n- `omarchy-webapp-handler-zoom`\n- `omarchy-webapp-install`\n- `omarchy-webapp-remove`\n\n### windows (1)\n- `omarchy-windows-vm`\n","# Omarchy Skill\n\nTreat 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.\n\n## Operating rules\n\n1. Start with command name matching and in-file comments under `\u002Fhome\u002Fachals\u002F.local\u002Fshare\u002Fomarchy\u002Fbin`.\n2. Prefer read-only\u002Fstatus commands first (`*list*`, `*status*`, `*current*`, `*available*`, `*version*`).\n3. Ask before broad or high-impact actions (`*install*`, `*remove*`, `*reinstall*`, `*update*`, `*pkg*`, `*setup*`, `*set*`).\n4. Avoid bulk discovery execution. Do static inspection first.\n5. Never assume `omarchy-*` scripts support standard CLI flags or parameters (including `--help`). Treat each script as custom; inspect its file\u002Fheader comments first.\n\n## Worked examples (good vs bad)\n\nUse 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.\n\n### 1) Restarting Waybar\n\nUser intent: \"Waybar is broken, restart it.\"\n\n- Bad (generic shortcut):\n  - `pkill waybar && waybar`\n- Good (Omarchy-native):\n  - `omarchy-restart-waybar`\n- Why: Omarchy wrappers usually handle environment\u002Fsession assumptions better than raw kill-and-relaunch one-liners.\n\n### 2) Applying config\u002FUI refresh after edits\n\nUser intent: \"I changed config, apply it.\"\n\n- Bad:\n  - restarting random processes manually until things look fixed\n- Good:\n  - use targeted refresh script first, e.g. `omarchy-refresh-waybar`, `omarchy-refresh-hyprland`, `omarchy-refresh-config` (pick by component)\n- Why: refresh scripts are explicit and reversible; manual shotgun restarts are noisy and risky.\n\n### 3) Package management task\n\nUser intent: \"Install\u002Fremove package X.\"\n\n- Bad:\n  - using raw `pacman`\u002F`yay` first without checking Omarchy wrappers\n- Good:\n  - inspect and prefer `omarchy-pkg-*` flow (`...-present`, `...-missing`, then `...-install`\u002F`...-remove`)\n- Why: wrapper flow keeps behavior consistent with Omarchy expectations.\n\n### 4) Theme change request\n\nUser intent: \"Switch theme \u002F sync theme to apps.\"\n\n- Bad:\n  - editing dotfiles manually first and restarting random apps\n- Good:\n  - `omarchy-theme-list` -> `omarchy-theme-set` -> app-specific follow-ups if needed (`omarchy-theme-set-vscode`, `...-browser`, `...-obsidian`)\n- Why: Omarchy theme pipeline may include extra integration steps beyond plain config edits.\n\n### 5) Audio\u002FBluetooth\u002FWi‑Fi issue\n\nUser intent: \"Audio\u002FBluetooth\u002FWi‑Fi stopped behaving.\"\n\n- Bad:\n  - broad process killing (`killall pipewire`, random daemon restarts)\n- Good:\n  - use targeted wrapper restarts such as `omarchy-restart-pipewire`, `omarchy-restart-bluetooth`, `omarchy-restart-wifi`\n- Why: targeted wrappers reduce collateral damage and match Omarchy’s service model.\n\n### 6) \"What command should I run?\" discovery flow\n\nUser intent: ambiguous request like \"fix my display stack\".\n\n- Bad:\n  - execute many commands to discover options (`for c in omarchy-*; do $c --help; done`)\n- Good:\n  1. Statically inspect names in `\u002Fhome\u002Fachals\u002F.local\u002Fshare\u002Fomarchy\u002Fbin`\n  2. Read top-of-file script comments for likely candidates\n  3. Start with read-only\u002Fstatus scripts\n  4. Propose 1-3 likely commands and ask before high-impact actions\n- Why: static inspection is safer, faster, and follows no-bulk-probing policy.\n\n### 7) Update workflow\n\nUser intent: \"Update system.\"\n\n- Bad:\n  - directly running full update steps without checking availability\u002Fstate\n- Good:\n  - check first: `omarchy-update-available` (and related status)\n  - then execute appropriate Omarchy update path with confirmation for impactful steps\n- Why: staged update flow reduces surprise breakage.\n\n## Decision template (apply every time)\n\nFor any Omarchy task, follow this mini-checklist:\n\n1. Identify component (UI, package, theme, network, update, device, etc.)\n2. Find matching `omarchy-*` family by name and script header comments\n3. Prefer read-only\u002Fstatus command first\n4. Use targeted `omarchy-refresh-*`\u002F`omarchy-restart-*` over raw kill\u002Frelaunch\n5. Ask before high-impact actions (`install\u002Fremove\u002Freinstall\u002Fupdate\u002Fsetup\u002Fset`)\n\n## Omarchy command catalog (static, local)\n\nTotal commands: **161**\n\n### battery (2)\n- `omarchy-battery-monitor`\n- `omarchy-battery-remaining`\n\n### branch (1)\n- `omarchy-branch-set`\n\n### channel (1)\n- `omarchy-channel-set`\n\n### cmd (12)\n- `omarchy-cmd-apple-display-brightness`\n- `omarchy-cmd-audio-switch`\n- `omarchy-cmd-first-run`\n- `omarchy-cmd-missing`\n- `omarchy-cmd-present`\n- `omarchy-cmd-reboot`\n- `omarchy-cmd-screenrecord`\n- `omarchy-cmd-screensaver`\n- `omarchy-cmd-screenshot`\n- `omarchy-cmd-share`\n- `omarchy-cmd-shutdown`\n- `omarchy-cmd-terminal-cwd`\n\n### debug (1)\n- `omarchy-debug`\n\n### dev (1)\n- `omarchy-dev-add-migration`\n\n### drive (3)\n- `omarchy-drive-info`\n- `omarchy-drive-select`\n- `omarchy-drive-set-password`\n\n### font (3)\n- `omarchy-font-current`\n- `omarchy-font-list`\n- `omarchy-font-set`\n\n### hibernation (3)\n- `omarchy-hibernation-available`\n- `omarchy-hibernation-remove`\n- `omarchy-hibernation-setup`\n\n### hook (1)\n- `omarchy-hook`\n\n### hyprland (3)\n- `omarchy-hyprland-window-close-all`\n- `omarchy-hyprland-window-pop`\n- `omarchy-hyprland-workspace-toggle-gaps`\n\n### install (9)\n- `omarchy-install-chromium-google-account`\n- `omarchy-install-dev-env`\n- `omarchy-install-docker-dbs`\n- `omarchy-install-dropbox`\n- `omarchy-install-steam`\n- `omarchy-install-tailscale`\n- `omarchy-install-terminal`\n- `omarchy-install-vscode`\n- `omarchy-install-xbox-controllers`\n\n### launch (14)\n- `omarchy-launch-about`\n- `omarchy-launch-audio`\n- `omarchy-launch-bluetooth`\n- `omarchy-launch-browser`\n- `omarchy-launch-editor`\n- `omarchy-launch-floating-terminal-with-presentation`\n- `omarchy-launch-or-focus`\n- `omarchy-launch-or-focus-tui`\n- `omarchy-launch-or-focus-webapp`\n- `omarchy-launch-screensaver`\n- `omarchy-launch-tui`\n- `omarchy-launch-walker`\n- `omarchy-launch-webapp`\n- `omarchy-launch-wifi`\n\n### lock (1)\n- `omarchy-lock-screen`\n\n### menu (2)\n- `omarchy-menu`\n- `omarchy-menu-keybindings`\n\n### migrate (1)\n- `omarchy-migrate`\n\n### notification (1)\n- `omarchy-notification-dismiss`\n\n### pkg (9)\n- `omarchy-pkg-add`\n- `omarchy-pkg-aur-accessible`\n- `omarchy-pkg-aur-add`\n- `omarchy-pkg-aur-install`\n- `omarchy-pkg-drop`\n- `omarchy-pkg-install`\n- `omarchy-pkg-missing`\n- `omarchy-pkg-present`\n- `omarchy-pkg-remove`\n\n### powerprofiles (1)\n- `omarchy-powerprofiles-list`\n\n### refresh (14)\n- `omarchy-refresh-applications`\n- `omarchy-refresh-chromium`\n- `omarchy-refresh-config`\n- `omarchy-refresh-fastfetch`\n- `omarchy-refresh-hypridle`\n- `omarchy-refresh-hyprland`\n- `omarchy-refresh-hyprlock`\n- `omarchy-refresh-hyprsunset`\n- `omarchy-refresh-limine`\n- `omarchy-refresh-pacman`\n- `omarchy-refresh-plymouth`\n- `omarchy-refresh-swayosd`\n- `omarchy-refresh-walker`\n- `omarchy-refresh-waybar`\n\n### reinstall (4)\n- `omarchy-reinstall`\n- `omarchy-reinstall-configs`\n- `omarchy-reinstall-git`\n- `omarchy-reinstall-pkgs`\n\n### remove (1)\n- `omarchy-remove-dev-env`\n\n### reset (1)\n- `omarchy-reset-sudo`\n\n### restart (15)\n- `omarchy-restart-app`\n- `omarchy-restart-bluetooth`\n- `omarchy-restart-btop`\n- `omarchy-restart-hyprctl`\n- `omarchy-restart-hypridle`\n- `omarchy-restart-hyprsunset`\n- `omarchy-restart-mako`\n- `omarchy-restart-opencode`\n- `omarchy-restart-pipewire`\n- `omarchy-restart-swayosd`\n- `omarchy-restart-terminal`\n- `omarchy-restart-walker`\n- `omarchy-restart-waybar`\n- `omarchy-restart-wifi`\n- `omarchy-restart-xcompose`\n\n### setup (3)\n- `omarchy-setup-dns`\n- `omarchy-setup-fido2`\n- `omarchy-setup-fingerprint`\n\n### show (2)\n- `omarchy-show-done`\n- `omarchy-show-logo`\n\n### snapshot (1)\n- `omarchy-snapshot`\n\n### state (1)\n- `omarchy-state`\n\n### theme (13)\n- `omarchy-theme-bg-install`\n- `omarchy-theme-bg-next`\n- `omarchy-theme-current`\n- `omarchy-theme-install`\n- `omarchy-theme-list`\n- `omarchy-theme-remove`\n- `omarchy-theme-set`\n- `omarchy-theme-set-browser`\n- `omarchy-theme-set-gnome`\n- `omarchy-theme-set-obsidian`\n- `omarchy-theme-set-templates`\n- `omarchy-theme-set-vscode`\n- `omarchy-theme-update`\n\n### toggle (5)\n- `omarchy-toggle-idle`\n- `omarchy-toggle-nightlight`\n- `omarchy-toggle-screensaver`\n- `omarchy-toggle-suspend`\n- `omarchy-toggle-waybar`\n\n### tui (2)\n- `omarchy-tui-install`\n- `omarchy-tui-remove`\n\n### tz (1)\n- `omarchy-tz-select`\n\n### update (14)\n- `omarchy-update`\n- `omarchy-update-analyze-logs`\n- `omarchy-update-available`\n- `omarchy-update-available-reset`\n- `omarchy-update-branch`\n- `omarchy-update-confirm`\n- `omarchy-update-firmware`\n- `omarchy-update-git`\n- `omarchy-update-keyring`\n- `omarchy-update-perform`\n- `omarchy-update-restart`\n- `omarchy-update-system-pkgs`\n- `omarchy-update-time`\n- `omarchy-update-without-idle`\n\n### upload (1)\n- `omarchy-upload-log`\n\n### version (4)\n- `omarchy-version`\n- `omarchy-version-branch`\n- `omarchy-version-channel`\n- `omarchy-version-pkgs`\n\n### voxtype (5)\n- `omarchy-voxtype-config`\n- `omarchy-voxtype-install`\n- `omarchy-voxtype-model`\n- `omarchy-voxtype-remove`\n- `omarchy-voxtype-status`\n\n### webapp (4)\n- `omarchy-webapp-handler-hey`\n- `omarchy-webapp-handler-zoom`\n- `omarchy-webapp-install`\n- `omarchy-webapp-remove`\n\n### windows (1)\n- `omarchy-windows-vm`\n",{"name":5,"description":7},"main","f9d3fe7cf9ac8f1ea63a0d96e98e1f510a3814db","skills\u002Fachals-iglu\u002Fomarchy",1,"https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills","https:\u002F\u002Fgithub.com\u002Fjavimosch","intrane.fr","Building robust, open-source infrastructure for the commons. AI-leveraged, self-hosted, built to last.","2026-06-07 03:34:58",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add javimosch\u002Fopen-claw-skills --skill omarchy",{"tool":39,"command":40},"bunx","bunx skills add javimosch\u002Fopen-claw-skills --skill omarchy",{"tool":42,"command":43},"pnpm","pnpm dlx skills add javimosch\u002Fopen-claw-skills --skill omarchy","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fachals-iglu\u002Fomarchy\u002FSKILL.md",true,[],[48,56,63,70,77,84],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":55},"01M778GGXG2VQ0YF31W2MKGMQZ","crowd-prompting","A marketplace where AI agents improve prompts, system instructions, tool descriptions, and other text-based content with domain expertise from real-world operations — and earn tokens for valuable contributions.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzzadrian\u002Fcrowd-prompting\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":55},"01M778G7BH8SBJ9FJ6C3G7CB1K","ceaser","Interact with the Ceaser privacy protocol on Base L2 using the ceaser-mcp MCP tools. This skill uses the ceaser-mcp npm package for ALL operations -- shield, unshield, note management, and protocol queries. All ceaser tool calls use CLI subcommands (npx -y ceaser-mcp \u003Csubcommand>). Ceaser is a privacy-preserving ETH wrapper using Noir\u002FUltraHonk zero-knowledge proofs on Base L2 (chain ID 8453).","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyra-v21\u002Fceaser\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":55},"01M778FYCJQZWFKKX5FYMK3S47","ceaser-send","Fully automated private ETH transfer via Ceaser Protocol on Base L2 using the ceaser-mcp MCP tools. This skill uses the ceaser-mcp npm package for ALL operations -- all ceaser tool calls use CLI subcommands (npx -y ceaser-mcp \u003Csubcommand>). WARNING -- creates observable on-chain links between user wallet and hot wallet (see Privacy Warning). Generates an ephemeral hot wallet with BIP-39 mnemonic recovery, user funds it, agent signs and broadcasts the Shield TX automatically. Exactly one manual step required (funding the hot wallet with ETH). Uses Noir\u002FUltraHonk zero-knowledge proofs.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyra-v21\u002Fceaser-send\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":55},"01M778FQQNSEYA3HJKZBPQ4M9Z","dilemm-ai","Compete in DilemmAI, the prisoner's dilemma AI arena at dilemm.ai. Use when an OpenClaw agent wants to create an account, design and submit strategy prompts for their bot, enter matchmaking, analyze historical matches and leaderboards, and iterate on bot strategy. Requires headless browser automation (no API available yet).","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyori\u002Fdilemm-ai\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":55},"01M778FGVZX7QA2TF9BFMM37FY","moldium","Post and manage content on the Moldium blog platform. Triggered by \"post to Moldium\", \"write a blog post\", \"publish an article\", etc.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyom45\u002Fmoldium\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":55},"01M778F88D8PQ9MQ0KNW2TJ8ZH","arxiv-paper-reviews","Interact with arXiv Crawler API to fetch papers, read reviews, submit comments, search papers, and import papers. Use when working with arXiv papers, fetching paper lists by date\u002Fcategory\u002Finterest, viewing paper details with comments, submitting paper reviews, searching papers by title, or importing papers from arXiv URLs via API at http:\u002F\u002Fweakaccept.top:8000\u002F.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzxrys\u002Farxiv-paper-reviews\u002FSKILL.md",[],[]]