github-auth

Configure GitHub authentication for Hermes Agent via git, gh CLI, or curl.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

GitHub authentication for Hermes Agent enables secure access to repositories, pull requests, issues, and CI workflows from the agent without exposing credentials in commands.

Core Features & Use Cases

  • Supports git HTTPS token and SSH key authentication for Git operations and PR interactions.
  • Integrates gh CLI login when available for richer API access and streamlined git credentials.
  • Provides clear fallback paths and validation via Hermes status for reliable, repeatable setup across servers.

Quick Start

Run the authentication setup to enable GitHub access for Hermes using either HTTPS/PAT or SSH, or via gh auth login, and verify readiness with Hermes status.

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 an AI agent to manage pull requests and issues?

To set up GitHub authentication for an AI agent, you configure git HTTPS tokens or SSH keys, use gh CLI login for API access, and store credentials in ~/.hermes/.env or git credential store. Validation via Hermes status ensures readiness.

What is the best way to authenticate with GitHub when gh CLI is unavailable?

When gh CLI is unavailable, the best way to authenticate with GitHub is using curl-based API calls as a fallback. This method relies on proper token scopes and git credential store to maintain access to repositories and CI workflows.

Do I need root permissions to install and configure GitHub credentials for Hermes Agent?

No, you do not need root permissions; non-root installation is explicitly required for configuring GitHub credentials. This ensures token storage in ~/.hermes/.env and git credential store remains secure and properly scoped for agent operations.

Does this GitHub authentication method support both SSH keys and personal access tokens?

Yes, this GitHub authentication method supports both SSH key and HTTPS personal access token workflows. It integrates git credentials and gh auth login to enable repository access, pull request interactions, and CI workflow automation via the agent.

What token scopes are required for GitHub authentication to enable CI workflows and PR interactions?

Proper token scopes are required to enable CI workflows and PR interactions, though specific scopes depend on repository access needs. The Skill validates these scopes through Hermes status after storing tokens in ~/.hermes/.env or git credential store.

Why does GitHub authentication fail when running the agent on a server environment?

GitHub authentication may fail on a server if installed as root, if token scopes are insufficient, or if gh CLI is missing without curl fallback configured. Validation via Hermes status helps identify and resolve these setup issues.