github-auth

Configure GitHub authentication for repository workflows with automatic method detection.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

GitHub work often stalls when the agent cannot authenticate for cloning, pushing, opening pull requests, or calling the API. This Skill removes that friction by setting up a reliable login path without requiring sudo or manual troubleshooting.

Core Features & Use Cases

  • Detects whether gh, token-based HTTPS, or SSH is available and chooses the best path automatically.
  • Configures git credentials, SSH keys, and gh auth for repository operations, pull request workflows, issue management, and CI access.
  • Provides curl-based API fallback when gh is unavailable and includes troubleshooting guidance for common permission and credential errors.
  • Useful when bootstrapping a new machine, switching between GitHub accounts, or enabling a headless server to work with private repositories.

Quick Start

Ask the agent to detect your current GitHub authentication method and configure the best available login path for repository work.

Frequently Asked Questions about github-auth

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

FAQPage Schema
How do I authenticate git for cloning private GitHub repositories on a headless server?

To authenticate git for private repositories on a headless server, this Skill configures HTTPS personal access tokens, SSH keys, or git credential helpers automatically. It detects the available environment and sets up the best login path without requiring sudo access.

What is the best way to configure GitHub authentication for automated agent workflows?

Configuring GitHub authentication for automated agent workflows involves detecting whether gh CLI, token-based HTTPS, or SSH is available. This Skill automatically selects the optimal login path and sets up credentials for seamless cloning, pushing, and pull request operations.

Can I use the gh CLI to manage pull requests and issues when gh is not installed?

When the gh CLI is not installed, you can use a curl-based API fallback to manage pull requests, issues, and API access. This Skill provides automatic environment detection and includes troubleshooting guidance for common credential errors.

Do I need sudo access to set up SSH keys and GitHub tokens for CI automation?

You do not need sudo access to set up SSH keys and GitHub tokens for CI automation. This Skill removes login friction by configuring git credentials and gh auth locally, establishing a reliable connection for repository and CI workflows.

How do I switch between multiple GitHub accounts on the same machine?

To switch between multiple GitHub accounts on the same machine, this Skill configures distinct git credentials, SSH keys, and gh auth profiles. It enables seamless transitions between login states for different repository workflows.

Why does my GitHub authentication fail when pushing commits via SSH?

GitHub authentication failures when pushing via SSH often stem from misconfigured SSH keys or credential helpers. This Skill detects your current setup, applies the correct login path, and provides troubleshooting guidance for common permission errors.