What problem does it solve? Setting up GitHub authentication is a common blocker before any repository work can begin, and the right method depends on which tools are installed and whether you have sudo access. This Skill detects the available tooling and walks through the correct authentication path so git operations, API calls, and gh CLI commands work without repeated credential prompts. ## Core Features & Use Cases - Automatic Detection: Checks for git, gh CLI, existing credentials, and auth status, then follows a decision tree to pick the right setup method. - Git-Only Authentication: Configures HTTPS personal access tokens with credential helpers or SSH keys with URL rewriting, requiring no sudo or extra installs. - gh CLI Authentication: Supports interactive browser login and token-based headless login, plus gh auth setup-git for unified credentials. - API Fallback via curl: Extracts tokens from the git credential store or environment variables to call the GitHub REST API when gh is unavailable. - Use Case: On a fresh headless server without sudo, use this Skill to create a personal access token, configure the git credential store, set commit identity, and verify push access in minutes. ## Quick Start Set up GitHub authentication on this machine so I can clone, push, and use the GitHub API.