← ClaudeAtlas

setup-herdrlisted

Install herdr (terminal-native agent multiplexer), set up its Claude Code and OpenCode integrations, and configure shell profiles to auto-launch herdr on startup (replacing any existing Zellij autostart block). Use when the user wants to install or configure herdr.
atman-33/workhub · ★ 1 · Data & Documents · score 77
Install: claude install-skill atman-33/workhub
## Task Install `herdr` (https://herdr.dev), a terminal-native agent multiplexer, wire up its Claude Code / OpenCode integrations, and configure shell profiles so `herdr` launches automatically on startup — replacing any existing Zellij autostart installed by `setup-zellij`. ## Environment note: this session can be hosted on either side This skill touches both a Windows environment and a WSL environment, and the agent session driving it can be hosted on **either** — the interop direction flips accordingly: - **Hosted in WSL:** reach Windows via `powershell.exe`/`pwsh.exe`, and read/edit Windows profile files directly at their `/mnt/c/...` path rather than shelling a multi-line edit through `powershell.exe -Command` — quoting an edit through a nested shell is fragile; a direct file edit is not (the same class of problem step 4's here-string warning describes). - **Hosted on Windows:** reach WSL via `wsl -- <command>`, as this skill's snippets show by default. Determine which applies once, then use the matching direction for every step below. The same preference — direct file access over a shell-quoted command — also applies to the idempotency checks in steps 1, 3, and 4: read a file's content and inspect it rather than piping it through `grep`/`Select-String` across the interop boundary. ## Steps ### 1. Check herdr installation (per environment) A PATH-only check false-negatives: herdr's own installer doesn't add itself to PATH (see step 2), so the binary can