github-auth

Name: github-auth
Availability: InStock
Author: attentiondotnet

Authenticate Hermes Agent with GitHub via HTTPS, SSH, or gh CLI.

Updated Mar 30, 2026

Search Tags:#git #authentication #github #ssh #gh-cli #credential

Ready to run

npx skills add https://github.com/attentiondotnet/hermes-agent --skill github-auth-attentiondotnet

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Authenticate Hermes Agent with GitHub to access repositories, PRs, and issues. This workflow eliminates manual login friction by enabling either a Git-based path or the gh CLI, ensuring the agent can operate with GitHub resources securely.

Core Features & Use Cases

Git-only authentication via HTTPS with Personal Access Tokens (PATs) or SSH keys for universal GitHub access.
gh CLI authentication when gh is installed, providing API access and integrated git credentials.
Automatic detection flow that checks gh auth status, token availability, and existing git credentials to select the best method.
Verification and setup steps that configure git identity and validate access for downstream tasks.

Quick Start

Run the Hermes Agent GitHub authentication setup and follow prompts to complete the chosen method.

Frequently Asked Questions about github-auth

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

FAQPage Schema

How do I authenticate an AI agent with GitHub using git or gh CLI?▼

GitHub authentication for an agent can be configured via git HTTPS with Personal Access Tokens, SSH keys, or gh CLI. An automatic detection flow selects the best method by checking gh auth status and existing git credential helpers.

What's the best way to set up GitHub credentials for automated repository access?▼

The best way to set up GitHub credentials is running an authentication setup that detects gh CLI availability and git credential helpers. This configures your git identity and exports credentials securely for downstream workflows accessing repositories, PRs, and issues.

Can I use SSH keys for GitHub authentication instead of a Personal Access Token?▼

Yes, SSH keys can be used for GitHub authentication instead of a PAT. The authentication setup supports a git-only path via SSH, providing universal GitHub access when gh CLI is not installed or when you prefer SSH key-based verification.

Do I need the gh CLI installed to configure GitHub authentication?▼

No, you do not need the gh CLI installed to configure GitHub authentication. The setup supports a git-only authentication path using HTTPS with Personal Access Tokens or SSH keys, ensuring access even without the gh CLI.

How does the git credential helper detection flow work for GitHub access?▼

The git credential helper detection flow checks gh auth status, token availability, and existing git credentials to select the optimal authentication method. It then configures git identity and validates access for downstream tasks.

Why is my GitHub authentication not working when accessing repositories from an agent?▼

GitHub authentication may fail if git identity is unconfigured or credential helpers are missing. The setup addresses this by verifying gh auth status, applying SSH or HTTPS PAT credentials, and validating access before exporting credentials for workflows.