github-auth

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

GitHub authentication is essential for the agent to interact with repositories, PRs, issues, and CI pipelines. It covers two pathways: git-based authentication (HTTPS tokens or SSH keys) and gh CLI authentication, enabling secure access across local machines, servers, or cloud runtimes.

Core Features & Use Cases

  • Git-based authentication supporting HTTPS with tokens or SSH keys for standard git operations.
  • gh CLI authentication for richer API access and simplified credential handling.
  • Automatic detection of available methods with safe fallbacks and clear verification steps.
  • Use cases include onboarding new machines, CI runners, and multi-repo workflows.

Quick Start

Begin by requesting authentication setup for a GitHub workflow and follow the prompts to choose between git-based or gh-based authentication.

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 operations using HTTPS tokens or SSH keys?

GitHub authentication can be configured using git HTTPS with tokens or SSH keys for standard repository operations. This setup enables secure access to repositories, PRs, and issues across local machines and servers.

Can I use gh CLI authentication instead of git credentials for repository access?

Yes, gh CLI authentication provides richer API access and simplified credential handling compared to standard git credentials. It supports secure interaction with repositories, PRs, issues, and CI pipelines.

What's the best way to authenticate a CI runner for GitHub workflows?

Authenticating a CI runner involves configuring either git HTTPS tokens, SSH keys, or gh auth. Automatic detection identifies available methods and applies safe fallbacks to ensure seamless CI workflow access.

Does GitHub authentication setup support automatic fallbacks across different environments?

GitHub authentication setup supports automatic detection of available methods with safe fallbacks across local machines, servers, and CI runtimes. This ensures clear verification steps and seamless repository access during onboarding.

Why do I need GitHub authentication for managing PRs and issues?

GitHub authentication is essential for the agent to interact with repositories, PRs, issues, and CI pipelines. It enables secure access and simplified credential handling across local machines, servers, or cloud runtimes.

Do I need gh and git installed to configure GitHub authentication?

Yes, configuring GitHub authentication requires gh, git, curl, and python3. These dependencies support both git-based and gh CLI authentication pathways for seamless repository access.