github-auth

Configure GitHub authentication via HTTPS tokens, SSH keys, or gh CLI.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

GitHub authentication setup becomes a blocker when agents need to clone, push, manage PRs, or call the GitHub API reliably across machines and tools.

Core Features & Use Cases

  • HTTPS auth with Personal Access Tokens: Configure git to use a token for repo access and workflows like fetching, pushing, and PR operations.
  • SSH key authentication: Generate or use SSH keys and rewrite GitHub URLs to use SSH for smoother git interactions.
  • gh CLI auth flow: Use gh when available for a unified login experience and API-capable operations.
  • API fallback without gh: Use curl with GITHUB_TOKEN when gh is not installed, enabling API access for other GitHub skills.

Use Case: You want an agent to manage PRs and issues from a fresh machine without admin privileges by setting up authentication once and then using git/gh/curl consistently for repository tasks.

Quick Start

Ask the assistant to run the github-auth skill and guide you through choosing HTTPS token auth or SSH key auth for your environment.

Frequently Asked Questions about github-auth

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

FAQPage Schema
How do I configure GitHub authentication for an automated agent on a fresh machine?

To configure GitHub authentication for agents, you can use this skill to set up either HTTPS personal access tokens or SSH keys, detecting available methods and populating required environment variables like GITHUB_TOKEN for reliable repository access.

What is the best way to authenticate to the GitHub API when the gh CLI is not installed?

The best way to authenticate to the GitHub API without the gh CLI is to use a curl fallback with a personal access token. This skill sets the GITHUB_TOKEN environment variable, enabling API access for other GitHub skills.

How do I set up SSH key authentication for git commands accessing GitHub repositories?

To set up SSH key authentication for GitHub, this skill generates or uses existing SSH keys and rewrites GitHub URLs to use SSH, ensuring smoother git interactions for cloning and pushing repositories without needing a personal access token.

Does this GitHub authentication method work across both git-only environments and machines with the gh CLI installed?

Yes, this GitHub authentication method works across both git-only environments and machines with the gh CLI installed. It detects available auth methods and applies the appropriate configuration for HTTPS tokens or SSH keys.

Do I need a personal access token to manage pull requests and issues from an automated workflow?

You need a personal access token to manage pull requests and issues from an automated workflow if using HTTPS auth. This skill configures git to use the token for repo access and PR operations, or uses SSH keys as an alternative.

Why do I need to populate environment variables like GH_AUTH_METHOD for GitHub access?

You need to populate environment variables like GH_AUTH_METHOD and GITHUB_TOKEN to establish a consistent authentication state. This allows agents to reliably access repositories, manage PRs, and call the GitHub API across different tools.