What problem does it solve?
GitHub authentication setup is a common blocker when you want an agent to work with repositories, PRs, issues, and GitHub Actions without repeated login prompts or broken permissions.
Core Features & Use Cases
- GitHub HTTPS token auth (recommended): Use a Personal Access Token to enable git operations and API access across repositories.
- SSH key auth: Configure SSH keys and rewrite remotes so the agent can authenticate via SSH instead of passwords/tokens.
- Optional gh CLI auth: If the GitHub CLI is installed, perform a browser or token-based login for richer GitHub API and git credential handling.
- API fallback without gh: Use curl with a token when gh is not available, matching the approach used by other GitHub skills.
Quick Start
Tell the agent to set up GitHub authentication so git and GitHub API calls work, using a Personal Access Token for HTTPS on your machine.