github-auth

Configure GitHub authentication using git or gh CLI with tokens, SSH keys, and credential helpers.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/Rawgrowth-Consulting/rawclaw-agent --skill github-auth-rawgrowth-consulting
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-auth
Source: https://github.com/Rawgrowth-Consulting/rawclaw-agent/tree/main/skills/github/github-auth
Command: npx skills add https://github.com/Rawgrowth-Consulting/rawclaw-agent --skill github-auth-rawgrowth-consulting

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Streamlines GitHub access for the agent by programmatically configuring authentication, eliminating manual credential setup and repeated prompts.

Core Features & Use Cases

  • Dual-path authentication: use git (HTTPS tokens or SSH keys) or the gh CLI for richer API access.
  • Automatic detection: selects the best available method based on installed tools and current auth state.
  • Credential management: guides secure handling of tokens and credentials for automated workflows.

Quick Start

Configure GitHub authentication for your environment by letting the agent detect and apply the optimal method.

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 automated agent environment?

Set up GitHub authentication by letting the agent detect available tools and configure credentials using either git or gh CLI. The skill automatically selects the optimal method to eliminate manual setup and repeated prompts.

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

Authenticating with GitHub via SSH keys or HTTPS tokens depends on available tools. The system supports both methods, automatically detecting credentials and applying the appropriate git workflow or gh CLI configuration for secure access.

Does GitHub authentication work if the gh CLI is unavailable or not installed?

Yes, GitHub authentication works if the gh CLI is unavailable by falling back to the native git workflow. It utilizes HTTPS tokens, SSH keys, and credential helpers to securely establish access without requiring gh.

Can I use an interactive browser login flow to configure git credentials?

Yes, you can use an interactive browser login flow to configure git credentials via the gh CLI path. This method securely stores credentials and provides richer API access for automated workflows.

Why does my automated workflow keep prompting for GitHub credentials during git operations?

Automated workflows prompt for GitHub credentials when helpers or tokens are unconfigured. Programmatically setting up authentication via SSH keys, HTTPS tokens, or gh CLI securely stores credentials and eliminates repeated prompts during git operations.