github-auth

Configure GitHub authentication via HTTPS tokens, SSH keys, or gh CLI.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, git, curl, python3, and includes scripts (resource) components.

What problem does it solve?

This Skill removes the friction of authenticating to GitHub so the agent can work with repositories, pull requests, issues, and CI without repeated login failures.

Core Features & Use Cases

  • Multiple Authentication Paths: Supports HTTPS personal access tokens, SSH keys, and gh CLI login depending on what is available on the machine.
  • Environment Detection: Checks whether gh is installed, whether the user is already authenticated, and whether git credentials or tokens are already present.
  • Practical GitHub Workflows: Helps users configure credentials, set git identity, verify access, and troubleshoot common auth problems across Linux, macOS, and Windows.
  • Use Case: A developer wants the agent to open a pull request on a fresh laptop; this Skill detects the available login method, sets up credentials, and confirms access before any repo action starts.

Quick Start

Ask the skill to detect your current GitHub authentication method and configure the safest available login path for the repository task you want to perform.

Frequently Asked Questions about github-auth

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

FAQPage Schema
How do I set up GitHub authentication for git and gh CLI on a new machine?

GitHub authentication configuration works by detecting whether gh CLI is installed and whether git credentials are already present, then applying the safest available login path. It supports HTTPS personal access tokens, SSH keys, and gh CLI login for repository operations.

What's the best way to authenticate to GitHub for pull requests and CI workflows?

Authenticating for pull requests and CI workflows is best handled by configuring gh CLI login with fallback to HTTPS personal access tokens or SSH keys when gh is unavailable. This prevents repeated login failures during repository operations.

Do I need gh CLI installed to configure GitHub personal access tokens?

You do not need gh CLI installed to configure GitHub personal access tokens. The setup detects if gh is unavailable and falls back to directly handling HTTPS tokens or SSH keys for git access.

Why does my git push fail with authentication errors after setting up a token?

Git push authentication errors after setting up a token often occur when credentials are not properly detected or git identity is unset. Troubleshooting verifies token presence, confirms access, and ensures credential setup is correctly applied to the repository.

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

You can use SSH keys instead of HTTPS tokens for GitHub repository access. The setup supports multiple authentication paths including SSH keys, detecting the available method on your machine and configuring it for safe repository operations.