github-auth

Configure GitHub authentication for automated agents via tokens, SSH keys, or gh CLI.

14|2|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/gquthier/CLAWG --skill github-auth-gquthier
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-auth
Source: https://github.com/gquthier/CLAWG/tree/main/skills/github/github-auth
Command: npx skills add https://github.com/gquthier/CLAWG --skill github-auth-gquthier

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

GitHub authentication for automated agents, enabling secure access to repositories, PRs, issues, and CI workflows without manual credential handling.

Core Features & Use Cases

  • Two authentication paths: a Git-based workflow using HTTPS tokens or SSH keys, and the gh CLI flow for API access and git credential management.
  • Automatic detection of available methods and guided setup, plus fallback to curl-based API access when gh is unavailable.
  • Verified configuration and troubleshooting guidance to ensure persistent credentials across sessions.

Quick Start

Initialize the authentication setup and let the system configure Git credentials or gh authentication based on 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 authenticate an automated agent to access GitHub repositories and CI workflows?

You can establish GitHub authentication for automated agents by configuring credentials via HTTPS tokens, SSH keys, or the gh CLI process. The system detects available methods and applies the correct path to access repositories, PRs, issues, and CI workflows.

What is the best way to set up GitHub authentication when the gh CLI is not installed?

When gh is unavailable, set up GitHub authentication using the Git-based HTTPS or SSH workflow. The system automatically detects the missing CLI and falls back to curl-based API access to maintain agent functionality.

Does this GitHub authentication method support both SSH keys and HTTPS tokens?

Yes, this GitHub authentication supports both SSH keys and HTTPS tokens. It provides a Git-based workflow for SSH or HTTPS credentials alongside the gh CLI flow, detecting your environment to configure the correct method.

How do I verify that my GitHub token or SSH key is working for automated git operations?

The authentication setup includes built-in verification steps to confirm your GitHub token or SSH key is working. These checks validate credentials and ensure persistent configuration across automated agent sessions.

Do I need python3 and curl to configure GitHub authentication for my agents?

Yes, you need python3 and curl to run the authentication scripts, particularly for the curl-based API access fallback. Git is required for credential management, while gh is optional but recommended for the full CLI workflow.

Why does my automated agent lose GitHub authentication between sessions?

Agents lose GitHub authentication between sessions due to non-persistent credentials. This setup provides guided configuration and troubleshooting to ensure git credentials or gh authentication remain valid and persistent across sessions.