What problem does it solve? Setting up GitHub authentication is a common blocker before any repository work can begin, and the right method varies depending on whether the gh CLI is installed, whether you have sudo access, and whether you prefer HTTPS tokens or SSH keys. This Skill detects the available tooling and walks through the correct authentication path so git operations, API calls, and CI workflows work without repeated credential prompts. ## Core Features & Use Cases - Automatic auth detection: Checks for gh CLI, existing gh sessions, git credential helpers, and stored tokens, then picks the right setup path. - Git-only authentication: Configures HTTPS personal access tokens with credential caching or SSH keys with URL rewriting, requiring no root access or extra installs. - gh CLI authentication: Handles interactive browser login or token-based headless login, plus git credential integration via gh auth setup-git. - API fallback with curl: Extracts tokens from the git credential store or VoiceOS env file so other GitHub skills can call the REST API without gh. - Use Case: On a fresh headless Linux server with no sudo, use this Skill to configure a personal access token with the git credential store, set your commit identity, and verify push access in minutes. ## Quick Start Set up GitHub authentication on this machine so I can clone, push, and work with my repositories.