github-auth

Configure GitHub authentication for HTTPS tokens, SSH keys, and gh CLI.

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

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 setting up GitHub access so the agent can work with repositories, pull requests, issues, and CI without repeated login failures or manual guesswork.

Core Features & Use Cases

  • Token-Based HTTPS Access: Helps users create and store personal access tokens for Git operations when GitHub password auth is unavailable.
  • SSH Key Setup: Guides key generation, GitHub key registration, connection testing, and SSH-based Git remotes for secure access.
  • gh CLI Login and Fallbacks: Supports browser login, token login, and direct API usage when gh is installed or when only git and curl are available.
  • Use Case: A user on a fresh machine can quickly authenticate, verify repository access, and proceed with PRs or issue workflows without sudo or complex manual setup.

Quick Start

Ask the skill to configure the best GitHub login method for your machine and verify that you can access the target repository.

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 repository and pull request workflows?

GitHub authentication can be set up using HTTPS personal access tokens, SSH key-based access, or gh CLI login. This configures credential storage and verifies API access to enable seamless repository and PR workflows without repeated login failures.

What's the best way to configure GitHub access on a headless server without a browser?

On a headless server, configure GitHub access using token-based HTTPS login or direct API usage with curl and git. This verifies authentication detection and fallback handling without requiring a browser-based login flow.

How do I create a GitHub personal access token for Git operations when password auth is unavailable?

To use Git operations when GitHub password auth is unavailable, you need to create a personal access token and store it for HTTPS access. This allows credential storage to handle repository cloning and pushing automatically.

Does this GitHub authentication setup work with both gh CLI and standard git commands?

Yes, the authentication setup supports gh CLI login alongside standard git commands. It applies credential verification and API access across local, desktop, and headless environments, providing fallbacks when gh is not installed.

Why does my GitHub SSH key authentication fail during repository cloning?

GitHub SSH key authentication fails if the key is not registered, connectivity is untested, or git remotes are misconfigured. Proper setup requires guiding key generation, GitHub key registration, and connection testing for secure access.