github-auth

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

6|Updated Apr 26, 2026

Search Tags:#git #authentication #github #ssh #token #gh-cli

Ready to run

npx skills add https://github.com/Strategic-Automation/arachne --skill github-auth-strategic-automation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: github-auth
Source: https://github.com/Strategic-Automation/arachne/tree/main/src/arachne/skills/default/github/github-auth
Command: npx skills add https://github.com/Strategic-Automation/arachne --skill github-auth-strategic-automation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Streamline GitHub access for autonomous agents by providing a robust, multi-path authentication workflow that adapts to the available tools (git over HTTPS with tokens, SSH keys, or the gh CLI) and ensures secure, seamless operations against GitHub.

Core Features & Use Cases

Dual-path authentication: use HTTPS tokens with git, SSH keys, or the gh CLI for API access.
Detection and fallback: automatically selects the best available method and falls back to alternatives without user intervention.
Verification & setup: provides guidance to configure credentials, set identity, and validate access to ensure smooth automation workflows.

Quick Start

Configure GitHub authentication on your host by selecting the available method (git with HTTPS token, SSH keys, or gh CLI) and verify access.

Frequently Asked Questions about github-auth

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

FAQPage Schema

How do I authenticate an automated agent with GitHub in a CI environment?▼

Authenticating an automated agent with GitHub in a CI environment requires configuring git over HTTPS with tokens, SSH keys, or the gh CLI. The workflow automatically detects available tools and falls back to alternative methods to ensure secure repository access without manual intervention.

What is the best way to configure GitHub authentication across local machines and remote servers?▼

Configuring GitHub authentication across local machines and remote servers is best handled by selecting the most suitable available method, such as HTTPS tokens or SSH keys. This workflow handles detection, credential setup, and identity configuration to provide reliable access across different environments.

Can I use the gh CLI for GitHub API access instead of SSH keys or HTTPS tokens?▼

Yes, you can use the gh CLI for GitHub API access instead of SSH keys or HTTPS tokens. The authentication workflow supports gh CLI alongside git over HTTPS and SSH, automatically selecting the best available method and providing browser-based authentication flows with fallbacks.

Why does my GitHub authentication workflow fail to fall back when SSH keys are unavailable?▼

GitHub authentication fallbacks fail when SSH keys are unavailable if the workflow cannot detect alternative credentials like HTTPS tokens or the gh CLI. The multi-path authentication process verifies available tools and automatically transitions to a working method to prevent access failures.

Do I need to install git or gh CLI before setting up GitHub repository access for automation?▼

You need to have git or the gh CLI installed on your host before setting up GitHub repository access for automation. The authentication workflow operates on local machines, CI environments, and remote servers where these tools are available, using them to establish secure credential configuration and verification.

Does this GitHub authentication workflow support both token-based and browser-based login flows?▼

Yes, this GitHub authentication workflow supports both token-based and browser-based login flows. It adapts to the available environment by handling git over HTTPS with tokens, SSH keys, and gh CLI browser-based authentication, ensuring complete detection, credential setup, and identity verification.