setup-herdr

Migrate and validate herdr config.toml files across machines and platforms.

1|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/psw7205/skills --skill setup-herdr-psw7205
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: setup-herdr
Source: https://github.com/psw7205/skills/tree/main/skills/setup-herdr
Command: npx skills add https://github.com/psw7205/skills --skill setup-herdr-psw7205

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Moving a finished herdr config.toml to another machine often fails silently: encoding changes during transfer, version mismatches reject unknown keys, and remote attach keybindings behave differently than expected. This Skill provides a verified procedure to port the config byte-exactly and confirm every key is actually accepted on the target version and platform. ## Core Features & Use Cases - Byte-exact transfer: Uses scp/rsync with timestamped backups to avoid BOM/UTF-16 encoding corruption that silently resets the entire config to defaults. - One-line 3-stage diagnosis: Interprets herdr config check output (parse error, unknown key, ok) to instantly判定 version compatibility without key-by-key comparison. - Remote attach key ownership: Explains that keybindings are client-owned (--remote-keybindings local|server), while [ui]/[theme] are server-owned, preventing misdirected edits. - Platform pitfalls: Covers Ctrl-S XON/XOFF flow control on Linux/WSL, Korean IME ASCII switching (Windows Korean-IME only), Windows OpenSSH re-authentication, and TOML subtable placement traps. - Use Case: You set up a new Windows machine and your herdr prefix key does nothing. The Skill walks you through locating the config path via herdr --help, copying the file byte-exactly, running herdr config check, and diagnosing whether the terminal or OS is swallowing the key chord. ## Quick Start Port my herdr config from this machine to the new one and verify with herdr config check that every key is accepted.

Frequently Asked Questions about setup-herdr

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate herdr config to a new machine?▼

Copy the config.toml byte-exactly using scp or rsync after backing up the target's existing file. Find the target path from the Config line in herdr --help, then run herdr config check to confirm all keys are accepted.

How do I verify herdr accepted my config file?▼

Run herdr config check. Output of 'config: ok' means every key was accepted, 'unknown config key X' flags version mismatches, and 'config parse error' means the whole config fell back to defaults.

Why does my herdr config reset to defaults after copying?▼

Shell redirection or PowerShell Set-Content/Out-File changes the encoding, adding a BOM or converting to UTF-16, which the TOML parser rejects. Transfer the file itself with scp or rsync instead of piping contents.

Does herdr remote attach use the server keybindings?▼

No, keybindings are client-owned by default in remote attach mode. Change the client machine's config, or pass --remote-keybindings server to use the server's keymap; UI and theme settings remain server-owned.

Why is my herdr prefix key not working on Linux or WSL?▼

Ctrl-S is consumed by XON/XOFF flow control before reaching the app. Add stty -ixon to your shell rc file, or check whether the outer terminal or desktop environment is capturing the key chord first.

Can I share one herdr config across macOS and Windows?▼

Yes, mostly. The switch_ascii_input_source_in_prefix option is a silent no-op on unsupported platforms, so one config can be shared; note Windows IME switching supports Korean IME only.