github-auth

Configure GitHub authentication using HTTPS tokens or SSH keys.

1|Updated Jun 9, 2026

Search Tags:#GitHub #SSH #Authentication #gh CLI #Setup

Ready to run

npx skills add https://github.com/aivos-xie/hermes-skills --skill github-auth-aivos-xie

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: github-auth
Source: https://github.com/aivos-xie/hermes-skills/tree/main/github/github-auth
Command: npx skills add https://github.com/aivos-xie/hermes-skills --skill github-auth-aivos-xie

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill unit solves the challenge of authenticating to GitHub, allowing the agent to work with repositories, pull requests, issues, and CI without manual intervention.

Core Features & Use Cases

Authentication: Supports HTTPS tokens and SSH keys for secure access.
gh CLI Integration: If installed, provides richer API access with a simpler auth flow.
Detection Flow: Automates the detection of authentication status and appropriate tools.

Quick Start

Run the 'setup-github-auth' command to configure GitHub authentication for the agent.

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 automated agent operations?▼

To set up GitHub authentication for agent operations, you can configure either an HTTPS token or SSH keys. Run the 'setup-github-auth' command to enable automated access to repositories, pull requests, issues, and CI.

Do I need the gh CLI installed to authenticate with GitHub?▼

You do not need the gh CLI installed to authenticate with GitHub, as HTTPS tokens and SSH keys are natively supported. However, utilizing the gh CLI provides a simpler auth flow and richer API access if detected.

What is the difference between using SSH keys and HTTPS tokens for GitHub access?▼

SSH keys and HTTPS tokens are both supported methods for GitHub access. The gh CLI can utilize either method, but configuring HTTPS tokens often provides simpler API integration, while SSH keys handle secure repository cloning operations.

How does the agent detect my current GitHub authentication status?▼

The agent detects your GitHub authentication status through an automated detection flow. It checks for existing credentials and identifies whether the gh CLI is installed to determine the appropriate authentication method.

Can I use this to grant an agent access to GitHub pull requests and CI?▼

Yes, you can use this to grant an agent access to GitHub pull requests and CI. Proper credential setup enables the agent to work with repositories, issues, and continuous integration without manual intervention.

Why does GitHub authentication fail without proper credential setup?▼

GitHub authentication fails without proper credential setup because valid HTTPS tokens or SSH keys are required for secure verification. The agent cannot access repositories, pull requests, or CI until these credentials are configured.