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 what 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, PRs, issues, and CI access work without repeated credential prompts. ## Core Features & Use Cases - Automatic detection: Checks for git, gh CLI, existing authentication status, and credential helpers before choosing a setup path. - Multiple auth methods: Supports HTTPS personal access tokens, SSH key generation and configuration, and gh CLI login (browser-based or token-based for headless servers). - API fallback without gh: Provides curl-based GitHub API access using a GITHUB_TOKEN environment variable when the gh CLI is unavailable. - Use Case: On a fresh headless Linux server with no sudo access, use this Skill to authenticate git with a personal access token, configure your commit identity, and verify push access to your repositories. ## Quick Start Set up GitHub authentication on this machine so I can clone, push, and work with my repositories.
