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.