What problem does it solve? Setting up GitHub authentication for an agent or developer environment involves multiple confusing paths — personal access tokens, SSH keys, gh CLI login, and credential helpers — and failures like blocked device flows or stale cached credentials waste time. This Skill provides a detection flow and step-by-step setup so Git operations and GitHub API calls work without repeated auth prompts. ## Core Features & Use Cases - Auth Detection Flow: Checks for git, gh CLI, existing credentials, and token sources (env vars, ~/.git-credentials, ~/.dag/.env) to determine the current auth method before doing anything. - Git-Only Setup: Configures HTTPS personal access tokens with credential helpers or SSH ed25519 keys with URL rewriting — no sudo or gh installation required. - gh CLI Login: Prefers one-command token-based login (gh auth login --with-token) and documents device-flow pitfalls with a background-process fallback recipe. - Use Case: An agent needs to clone a repo and open a pull request on a fresh machine. It runs the detection script, finds no auth, walks the user through creating a token, stores it via the credential helper, and verifies push access. ## Quick Start Set up GitHub authentication on this machine so I can clone repos and push commits without being prompted for credentials.