github-auth

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

174|23|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/RedWoodOG/Hermes-Desktop --skill github-auth-redwoodog
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-auth
Source: https://github.com/RedWoodOG/Hermes-Desktop/tree/main/skills/github/github-auth
Command: npx skills add https://github.com/RedWoodOG/Hermes-Desktop --skill github-auth-redwoodog

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Enables reliable GitHub authentication for the Hermes Agent, allowing secure access to repositories, PRs, issues, and CI workflows across git and gh-based workflows.

Core Features & Use Cases

  • Git-based authentication: HTTPS with tokens or SSH keys for universal git operations.
  • gh CLI authentication: Browser-based login or token-based setup for richer API access.
  • Automatic method detection: Detects available tools and selects the optimal authentication path.
  • Use Case: Enable the agent to clone repos, create PRs, review issues, and trigger actions without manual credential setup.

Quick Start

Instruct the agent to configure GitHub authentication using your preferred method (git with HTTPS or SSH, or the gh CLI) and verify the setup.

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 agent to access repositories and PRs?

GitHub authentication is set up by configuring git with HTTPS tokens or SSH keys, or by using the gh CLI. The system features automatic method detection to choose the best authentication path for enabling repository access and PR workflows.

What is the best way to authenticate with GitHub using gh CLI or SSH keys?

The best way to authenticate depends on available tools: gh CLI offers browser-based or token setup for richer API access, while git with SSH keys or HTTPS tokens handles universal git operations. Automatic detection selects the optimal method.

Do I need gh CLI installed to configure GitHub authentication for my workflows?

No, gh CLI is not strictly required. While gh CLI provides browser-based login and richer API access, you can alternatively authenticate using git with HTTPS tokens or SSH keys for universal git operations across your environments.

Can I use HTTPS tokens instead of SSH keys for git repository access?

Yes, HTTPS tokens can be used instead of SSH keys for git-based authentication. The system supports token-based HTTPS authentication to provide universal git operations, allowing you to clone repos and trigger actions without manual SSH setup.

Why does my GitHub authentication method selection matter for CI workflows?

GitHub authentication method selection matters because gh CLI enables richer API access for PRs and issues, while git with HTTPS or SSH handles universal git operations. Automatic detection ensures the optimal path is chosen for CI workflow integration.