What problem does it solve?
GitHub authentication setup becomes a blocker when agents need to clone, push, manage PRs, or call the GitHub API reliably across machines and tools.
Core Features & Use Cases
- HTTPS auth with Personal Access Tokens: Configure git to use a token for repo access and workflows like fetching, pushing, and PR operations.
- SSH key authentication: Generate or use SSH keys and rewrite GitHub URLs to use SSH for smoother git interactions.
- gh CLI auth flow: Use
gh when available for a unified login experience and API-capable operations.
- API fallback without gh: Use
curl with GITHUB_TOKEN when gh is not installed, enabling API access for other GitHub skills.
Use Case: You want an agent to manage PRs and issues from a fresh machine without admin privileges by setting up authentication once and then using git/gh/curl consistently for repository tasks.
Quick Start
Ask the assistant to run the github-auth skill and guide you through choosing HTTPS token auth or SSH key auth for your environment.