github-auth

Authenticate with GitHub using HTTPS tokens, SSH keys, or gh CLI.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires curl, git, python3, grep, sed, cut, tr, head, and includes scripts (resource) components.

What problem does it solve?

GitHub authentication is a prerequisite for Hermes Agent to work with GitHub repositories, PRs, issues, and CI workflows. It provides a guided setup for both Git operations via HTTPS tokens or SSH keys, and gh CLI authentication when available.

Core Features & Use Cases

  • Supports git HTTPS tokens, SSH keys, and gh auth flows to enable seamless access to GitHub resources.
  • Automates switching between authentication methods based on environment capabilities and existing credentials.
  • Use case: configure a new CI agent to push code, open PRs, and manage issues across multiple GitHub repos without re-entering credentials.

Quick Start

Install Git, decide between HTTPS tokens or SSH keys, and run the built-in setup to authenticate with GitHub.

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 a new CI agent using git HTTPS or SSH?

GitHub authentication setup uses an environment-detection script to guide configuration of git HTTPS tokens or SSH keys, allowing CI agents to access repositories and workflows without manual credential re-entry.

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

GitHub authentication via HTTPS tokens uses generated personal access strings for git operations, while SSH keys rely on cryptographic key pairs; the Skill detects existing credentials and automates switching between these methods.

Can I use the gh CLI for GitHub authentication instead of git over HTTPS or SSH?

Yes, you can use gh CLI flows for GitHub authentication; the Skill supports gh auth as a fallback when available, detecting environment capabilities to switch between standard git and gh CLI methods.

Do I need curl and python3 installed to configure GitHub auth tokens and SSH keys?

Yes, curl and python3 are required dependencies to run the environment-detection script for GitHub auth setup, which determines the best authentication method and executes fallback logic.

When should I use gh CLI flows instead of standard git HTTPS tokens for GitHub access?

You should use gh CLI flows when standard git HTTPS tokens are unavailable or unsupported in your environment, utilizing the Skill's fallback logic to ensure seamless access to GitHub repositories and PRs.

Why is GitHub authentication necessary for accessing repositories, PRs, and CI workflows?

GitHub authentication is a prerequisite to verify identity and permissions, allowing automated agents or local machines to securely access repositories, PRs, issues, and CI workflows without hitting unauthorized access errors.