Manages SSH access, deployment, and dotfiles sync across a Tailscale-connected machine fleet.
npx skills add https://github.com/jlui17/dotfiles --skill dev-machines-jlui17
Please help me install this Agent Skill. Skill: dev-machines Source: https://github.com/jlui17/dotfiles/tree/main/agents/skills/dev-machines Command: npx skills add https://github.com/jlui17/dotfiles --skill dev-machines-jlui17
dev-machines list shows every registered machine with its tailnet host, ssh target, OS, role, and online status; dev-machines whoami identifies which machine the current session is running on. - Fleet Rollout: dev-machines sync pushes dotfiles changes to the other machines, and dev-machines herdr-add registers them in the local herdr client for a fleet-wide view. - Per-Host Safety Rules: Documents auth methods (Tailscale SSH vs public-key), production cautions for the srv host (approval before restarts or deploys, root-only docker), and the scorecard-mac keychain limitation with a herdr-pane workaround. - Use Case: You ask your agent to check the openclaw gateway on your server. It runs dev-machines whoami, looks up the srv host in the registry, reads state over Tailscale SSH, and knows to wait for your approval before restarting anything. ## Quick Start Ask the agent to run dev-machines whoami and then check the status of the openclaw service on your server over the tailnet.High-intent search queries and answers about installing and using this skill.
Use the ssh target from the machine registry with Tailscale SSH, which authenticates via tailnet identity without keys or passwords. Adding -o BatchMode=yes makes it safe for scripted, non-interactive use.
Run dev-machines sync to push dotfiles changes from the current machine to the other registered machines in the fleet. Use dev-machines list first to confirm which hosts are online and reachable.
An SSH login creates its own macOS security session where the login keychain holding the gh token stays locked, so private repo fetches fail. Run the command in a herdr pane instead, since the herdr LaunchAgent runs inside the unlocked desktop session.
Reading state on the production srv host is always fine, but restarts, deploys, and config changes require explicit approval first. Docker commands there also need root, reached via ssh root@<host> since root is not in the registry.
Run dev-machines whoami before anything else to identify the current machine. The ssh targets and cautions that apply depend on which registered machine the session is on, and the laptop is deliberately unregistered.
phnx-labsSynchronize SSH device profiles from Tailscale for fleet-wide command execution.
kfallahDeploy the CLaaS Tinker stack with Docker Compose for GPU-free operation.
blalorControls Herdr panes, tabs, workspaces, and coding-agent sessions via the installed CLI.
dmzoneillDiagnose remote host health via SSH, Ansible, and network scans.