github-auth

Configure GitHub authentication for git and gh CLI access.

Updated May 14, 2026
One-click install
npx skills add https://github.com/SethyPagna/Secretary-Jarvis --skill github-auth-sethypagna
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-auth
Source: https://github.com/SethyPagna/Secretary-Jarvis/tree/main/src/capabilities/skills/github/github-auth
Command: npx skills add https://github.com/SethyPagna/Secretary-Jarvis --skill github-auth-sethypagna

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

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

Core Features & Use Cases

  • HTTPS token setup for machines that only have git installed.
  • SSH key setup for users who prefer key-based access.
  • gh CLI login and detection for richer API access and simpler credential handling.
  • Use case: A developer can authenticate once on a new workstation and immediately push changes, open pull requests, and query GitHub data.

Quick Start

Use the github-auth skill to detect the available GitHub auth method and configure secure access for the current 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 git and gh CLI on a new machine?

Set up GitHub authentication by configuring HTTPS personal access tokens, SSH keys, or gh CLI login credentials. This enables secure local git access, repository work, pull requests, and API-backed automation without repeated login failures.

What's the best way to authenticate gh CLI and git on a headless server?

Authenticate gh CLI and git on headless environments by using HTTPS personal access tokens or SSH keys. Credential detection identifies available auth methods to enable secure Git operations and API calls without interactive browser login.

Do I need a personal access token or SSH key to configure GitHub authentication?

You need either a personal access token for HTTPS setup or an SSH key for key-based access. The authentication process detects available credentials and configures the appropriate method for git and gh CLI.

Can I use gh CLI login to manage pull requests and issues without git authentication?

Gh CLI login provides richer API access for pull requests, issue management, and CI queries independently. However, configuring git authentication alongside gh CLI enables full repository work including pushing changes and cloning.

Why does GitHub authentication fail when pushing changes or opening pull requests?

GitHub authentication fails when credentials are missing, expired, or undetected. Configuring HTTPS tokens, SSH keys, or gh CLI login resolves login friction and enables immediate push, pull request, and issue operations.

Does GitHub authentication setup work with both HTTPS and SSH on desktop and headless environments?

GitHub authentication setup works across desktop and headless environments supporting both HTTPS personal access tokens and SSH keys. Credential detection identifies the available method to configure secure access for the current machine.