github-auth

Authenticate with GitHub for Git operations and gh access.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

GitHub authentication ensures Git operations and gh API access can securely authenticate across environments, simplifying access to repositories and workflows.

Core Features & Use Cases

  • HTTPS token + SSH key support: enables safe, persistent Git credentials for push/pull.
  • gh CLI authentication integration: provides seamless API access and git credential management when gh is installed.
  • Guided credential workflows: ensures correct configuration across local machines, CI, and servers for reliable automation.

Quick Start

Configure GitHub authentication for your environment so you can securely push, pull, and automate GitHub workflows.

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 push and pull operations?

GitHub authentication for Git can be set up using HTTPS tokens or SSH keys. This provides safe, persistent credentials for repository push and pull operations across local machines, CI, and servers.

Can I use the gh CLI to manage Git credentials and API access?

Yes, gh CLI authentication integrates seamlessly to provide API access and Git credential management. When gh is installed, it enables guided credential workflows for reliable automation.

Do I need gh installed to configure GitHub authentication on a server?

No, gh is optional for GitHub authentication on servers. You can configure HTTPS tokens or SSH keys independently, though gh provides additional seamless API access and git credential management.

What's the best way to authenticate GitHub for CI and automation workflows?

The best way to authenticate GitHub for CI is using guided credential workflows with HTTPS tokens or SSH keys. This ensures correct configuration across servers for reliable and secure automation.

Does GitHub authentication support both HTTPS tokens and SSH keys?

Yes, GitHub authentication supports both HTTPS tokens and SSH keys. This enables safe, persistent Git credentials for push and pull operations across local development, CI, and server environments.

Why does GitHub authentication require network access during setup?

GitHub authentication requires network access to GitHub to validate credentials. Whether applying HTTPS tokens, SSH keys, or gh login, the setup process verifies access against GitHub's remote servers.