github-auth

Configure GitHub authentication for HTTPS, SSH, or gh CLI setups.

Updated Jul 7, 2026
One-click install
npx skills add https://github.com/TitoPrausee/nexus-toti --skill github-auth-titoprausee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-auth
Source: https://github.com/TitoPrausee/nexus-toti/tree/main/data/skills/github/github-auth
Command: npx skills add https://github.com/TitoPrausee/nexus-toti --skill github-auth-titoprausee

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill removes the friction of setting up reliable GitHub authentication so an agent can safely work with repositories, pull requests, issues, and CI without repeated login failures.

Core Features & Use Cases

  • Automatic auth detection: Identifies whether GitHub CLI, token-based HTTPS, or SSH access is already available and chooses the best path.
  • Multiple setup methods: Supports git-only authentication, SSH key setup, and GitHub CLI login for both desktop and headless environments.
  • Workflow readiness: Prepares credentials, identity settings, and repository access for tasks like pushing code, reviewing PRs, and managing GitHub resources.
  • Example use case: A developer on a new machine can use this Skill to authenticate once and immediately start cloning repos, creating branches, and pushing changes.

Quick Start

Use this skill to detect the best GitHub authentication method on the current machine and configure it for secure repository access.

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 a headless environment?

GitHub authentication for headless environments is configured using token-based HTTPS or SSH keys. This Skill detects available credentials and applies the best method for non-interactive repository access.

What is the best way to set up GitHub CLI for secure repository access?

The best way to set up GitHub CLI is by detecting existing credentials and applying fallback selection. This workflow configures gh CLI for secure repository operations, pull requests, and issues.

Does this GitHub authentication setup support both SSH key and credential helper methods?

Yes, this GitHub authentication setup supports SSH key, credential helper, and HTTPS token methods. It automatically detects existing configurations and selects the optimal path for repository access.

Why does my git authentication fail when pushing code in an automated workflow?

Git authentication fails in automated workflows when credentials are not exported to the environment. This Skill resolves this by configuring credential helpers and identity settings for headless use.

Can I use git and curl to authenticate with GitHub without the gh CLI?

Yes, you can authenticate without the gh CLI using git and curl for HTTPS token setup. This Skill configures git-only authentication and credential helpers for secure repository operations.

When do I need to configure a credential helper for GitHub repository access?

You need to configure a credential helper for GitHub repository access when avoiding repeated login failures during interactive or headless tasks. This Skill prepares credentials for pushing code and managing resources.