github-auth

Configure GitHub authentication for Hermes Agent using tokens or SSH keys.

Updated Jun 15, 2026
One-click install
npx skills add https://github.com/faramirezs/talking_printer --skill github-auth-faramirezs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-auth
Source: https://github.com/faramirezs/talking_printer/tree/main/hermes-agent/skills/github/github-auth
Command: npx skills add https://github.com/faramirezs/talking_printer --skill github-auth-faramirezs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

GitHub authentication across git HTTPS/SSH and the gh CLI can be painful and error-prone. This Skill streamlines getting authenticated so Hermes Agent can access repositories, pull requests, issues, and CI workflows without repeated prompts.

Core Features & Use Cases

  • Supports dual paths: Git-Only (HTTPS token or SSH) and gh CLI (when installed) for API access and git credentials.
  • Detects existing authentication status and selects the best method automatically.
  • Provides setup guidance for tokens and SSH keys, plus verification steps to confirm access.

Quick Start

Configure GitHub authentication for your environment using tokens or SSH keys, and optionally enable gh CLI login.

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 pull requests?

GitHub authentication can be set up using either Git-Only methods like HTTPS tokens and SSH keys, or the gh CLI. This approach detects existing credentials and guides you through setup to access repositories, pull requests, and CI workflows.

What's the best way to authenticate with GitHub using SSH keys or HTTPS tokens?

The best way to authenticate with GitHub is using HTTPS tokens for Git-Only access or SSH keys for secure repository interactions. This dual-path method automatically detects your existing authentication state and selects the optimal credential setup.

Does gh CLI work with Git-Only authentication for accessing GitHub issues and CI workflows?

Yes, gh CLI works alongside Git-Only authentication to provide API access and git credentials. It is used when available, while HTTPS tokens and SSH keys serve as alternative paths for accessing issues and CI workflows.

Why does GitHub authentication fail when switching between SSH and HTTPS token methods?

GitHub authentication can fail if existing credentials are not properly detected before switching methods. This setup process verifies your current authentication state and provides guided steps to correctly configure SSH keys or HTTPS tokens.

Can I detect existing GitHub authentication status before generating new SSH keys or tokens?

Yes, you can detect existing GitHub authentication status before generating new credentials. The process automatically checks your current authentication state for SSH keys and HTTPS tokens to prevent duplicate setup and ensure valid access.

How to verify GitHub token and SSH key setup for accessing repositories?

To verify GitHub token and SSH key setup, the authentication process includes built-in verification steps. These steps confirm that your configured HTTPS tokens or SSH keys successfully grant access to your target repositories and pull requests.