github-auth

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

Updated Aug 22, 2026
One-click install
npx skills add https://github.com/vivekgoquest/hermes-agent-stable --skill github-auth-vivekgoquest
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-auth
Source: https://github.com/vivekgoquest/hermes-agent-stable/tree/main/skills/github/github-auth
Command: npx skills add https://github.com/vivekgoquest/hermes-agent-stable --skill github-auth-vivekgoquest

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Setting up GitHub authentication on a new machine is error-prone, especially on headless servers or agent-driven sessions where interactive logins hang. This Skill walks through every authentication path so git operations, PRs, issues, and CI access work without repeated credential prompts. ## Core Features & Use Cases - Multiple Auth Methods: Supports HTTPS personal access tokens, SSH keys, and gh CLI login including a manual OAuth device flow for headless environments. - Automatic Detection: Detects existing auth state (gh CLI, GITHUB_TOKEN, git credential store) and picks the right method via the gh-env.sh helper script. - Headless Fallbacks: Handles known pitfalls like gh auth login hanging on keyring-less Linux boxes by writing hosts.yml directly, and Windows PTY Enter-key issues. - Use Case: You are on a fresh $5 VPS with no sudo and no browser. The Skill guides you through creating a personal access token, configuring the git credential helper, and verifying push access — no gh installation required. ## Quick Start Set up GitHub authentication on this machine so I can clone, push, and open pull requests without being prompted for credentials.

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 with GitHub without a password?▼

GitHub disabled password authentication, so use a personal access token as the password with the git credential helper set to store, or switch to SSH key authentication. Tokens need the repo scope for push access and workflow scope for GitHub Actions.

How to log in to gh CLI on a headless server?▼

Use the OAuth device flow: request a device code via curl, have the user enter it at github.com/login/device, then poll for the access token. If gh auth login --with-token hangs on a keyring-less system, write the token directly to ~/.config/gh/hosts.yml instead.

Should I use SSH keys or HTTPS tokens for GitHub?▼

HTTPS personal access tokens are the most portable and work everywhere without SSH configuration. SSH keys suit users who already have keys set up or prefer key-based auth, and can be combined with URL rewriting so HTTPS remotes use SSH automatically.

Why does git push keep asking for a password on GitHub?▼

GitHub no longer accepts account passwords for git operations. Use a personal access token as the password, and ensure git config credential.helper is set to store or cache so credentials persist across sessions.

Can I use the GitHub API without installing gh CLI?▼

Yes, the full GitHub API works with curl and a personal access token passed as an Authorization header. The token can be exported as GITHUB_TOKEN or extracted from the git credential store using the included helper script.

Why does gh auth login hang on my Linux VPS?▼

On headless systems without a secret-service keyring, gh's credential storage can block indefinitely even with --insecure-storage. Wrap the command in timeout 20 and fall back to writing ~/.config/gh/hosts.yml directly, which gh auth status reads without the keyring.