github-auth

Authenticate the agent to GitHub using git credentials or the gh CLI.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/overviewlabs/WHOX --skill github-auth-overviewlabs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-auth
Source: https://github.com/overviewlabs/WHOX/tree/main/skills/github/github-auth
Command: npx skills add https://github.com/overviewlabs/WHOX --skill github-auth-overviewlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures the agent can securely authenticate with GitHub so it can read and manipulate repositories, issues, and CI pipelines without manual login.

Core Features & Use Cases

  • Dual authentication paths: supports git HTTPS tokens, SSH keys, and the gh CLI for richer access.
  • Automated detection: detects whether gh is installed and authenticated and selects the best method automatically.
  • Workflow readiness: provides guidance on configuring credentials, tokens, and identities for seamless automation.

Quick Start

Run the authentication setup to connect the agent to GitHub using either gh (if installed) or git HTTPS/SSH.

Frequently Asked Questions about github-auth

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I authenticate an agent to GitHub using gh CLI or git credentials?

GitHub authentication can be established by running the automated setup, which detects whether the gh CLI is installed and authenticated, or configures git HTTPS tokens and SSH keys for secure repository access.

What is the best way to configure persistent GitHub credentials for automation?

To configure persistent GitHub credentials, the automated detection flow evaluates token management and credential helpers to establish secure, lasting access for automating CI workflows and pull requests.

Can I use SSH keys instead of HTTPS tokens for GitHub authentication?

Yes, dual authentication paths support both git HTTPS tokens and SSH keys, allowing the agent to automatically detect and select the most suitable method for your environment.

Does the agent need gh CLI installed to access GitHub repositories and issues?

No, gh CLI is not strictly required; the agent can use git HTTPS or SSH credentials, though the automated detection flow will leverage gh CLI if it is installed and authenticated for richer access.

Why does my GitHub authentication fail when switching between SSH and HTTPS?

Authentication failures often stem from conflicting credential helpers or missing token management; the skill's detection flow checks environment credentials to ensure proper configuration and prevent access issues.