What problem does it solve? Setting up recurring backups for a live website involves coordinating SSH keys, database credentials, and git pulls across two servers, and mistakes like reusing the wrong key or missing an auto-created commit on the live site are easy to make. This Skill provides the exact workflow for wiring a new site into an existing backup infrastructure without breaking conventions or other sites. ## Core Features & Use Cases - New site onboarding: Surveys existing backup.conf conventions, generates dedicated SSH keypairs, and creates the site folder and config on the backups machine. - First-run verification: Runs mysqlbk and pull manually and checks table counts and git HEAD against the live server before trusting the setup. - Ongoing orchestration: Uses full-backup with --process-subfolders to sweep many sites at once, and check-backup for read-only status. - Use Case: You inherit a new OpenCart client site and need nightly backups. Follow the workflow to reuse or create the right SSH key, write a backup.conf matching existing patterns, and verify the first dump and git pull succeed. ## Quick Start Set up backups for the new client site by surveying existing backup.conf files on the backups machine and creating a matching config with verified first mysqlbk and pull runs.