github-auth

Configure GitHub authentication for git and gh with tokens, SSH keys, and credential helpers.

3|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/ever-oli/io --skill github-auth-ever-oli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-auth
Source: https://github.com/ever-oli/io/tree/main/skills/github/github-auth
Command: npx skills add https://github.com/ever-oli/io --skill github-auth-ever-oli

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Set up reliable GitHub authentication for automated agents, covering both Git operations and GitHub API access to ensure seamless workflows.

Core Features & Use Cases

  • Two authentication paths: gitHTTPS with tokens or SSH keys, and gh CLI with optional browser login.
  • Detection & fallback: automatically detects installed tools and configures the appropriate flow; supports switching between methods as needed.
  • Credential safety & verification: configures credential helpers, validates authentication status, and provides setup notes for identity details.

Quick Start

Run the github-auth skill to initialize a robust GitHub authentication setup using git or gh on your machine.

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?

To set up GitHub authentication for an automated agent, you configure credentials across git and gh using either HTTPS tokens, SSH keys, or browser-based login. This process detects installed tools and applies the appropriate flow for pushing to private repos or managing PRs.

What is the best way to authenticate gh CLI and git for automation?

The best way to authenticate gh CLI and git for automation is using a dual-path approach that detects installed tools and configures appropriate fallback flows. This ensures robust credential storage and validates authentication status for both API access and direct repository operations.

Can I switch between SSH keys and HTTPS tokens for GitHub access?

Yes, you can switch between SSH keys and HTTPS tokens for GitHub access. The configuration supports switching between authentication methods as needed, automatically detecting the active setup and applying fallback flows to maintain secure credential helper operations.

Does this GitHub authentication setup handle credential storage and validation?

Yes, this GitHub authentication setup handles credential storage and validation. It configures credential helpers, validates the authentication status across git and gh, and provides setup notes for identity details to ensure safe and reliable automated workflows.

When do I need to configure GitHub credentials for cloning private repos?

You need to configure GitHub credentials for cloning private repos when your automation must access restricted repositories. This setup satisfies installation checks and token generation steps, ensuring automated agents can securely clone private data or push changes via git or gh.