What problem does it solve? Setting up GitHub authentication on a new or headless machine is error-prone: password auth is disabled, gh CLI logins can hang on keyring-less systems, and agents need a reliable way to detect which auth method is available. This Skill walks through token, SSH, and gh CLI setup with proven fallbacks. ## Core Features & Use Cases - Multiple Auth Paths: Covers HTTPS personal access tokens with git credential helpers, SSH key generation and configuration, and gh CLI login including the OAuth device flow for headless sessions. - Auth Detection Helpers: Ships a sourceable bash script (gh-env.sh) that detects the active auth method, resolves the GitHub username, and extracts repo owner/name from the git remote, plus a Python script that safely parses tokens from ~/.git-credentials. - Headless Fallbacks: Documents the hosts.yml workaround for when gh auth login --with-token hangs on keyring-less Linux systems, and curl-based API access when gh is not installed. - Use Case: An agent lands on a fresh VPS with no sudo and no browser. It detects gh is missing, guides the user to create a personal access token, configures the git credential store, and verifies push access — all without interactive prompts. ## Quick Start Set up GitHub authentication on this machine so I can clone, push, and work with my repositories.