github-auth

Authenticate the agent to GitHub for repository, PR, and CI operations.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/AVOI-CEO/avoi-agent --skill github-auth-avoi-ceo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-auth
Source: https://github.com/AVOI-CEO/avoi-agent/tree/main/skills/github/github-auth
Command: npx skills add https://github.com/AVOI-CEO/avoi-agent --skill github-auth-avoi-ceo

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Establishes a reliable GitHub authentication method for the agent so it can perform git operations, PR actions, and API calls without manual credential handling.

Core Features & Use Cases

  • Git-based authentication (HTTPS with tokens or SSH keys) for universal git operations.
  • gh CLI authentication when available, offering richer API access.
  • Automated detection flow to select the best method based on environment.
  • Clear setup guidance for both interactive and headless environments.

Quick Start

Choose the available authentication method (git-HTTPS, SSH, or gh) and verify authentication to enable repository interactions.

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 automated git operations and API calls?▼

GitHub authentication is established by detecting installed tools and selecting the best available method, such as git-HTTPS, SSH keys, or gh CLI, to enable repository operations without manual credential prompts.

What's the best way to authenticate an agent to GitHub in a headless container environment?▼

Authenticating in a headless container environment uses automated detection to select a viable path like git-HTTPS with tokens or gh CLI, providing safe configuration steps and optional fallbacks for environments without interactive prompts.

Does this GitHub authentication method support both git commands and gh CLI API access?▼

Yes, GitHub authentication supports both universal git operations using HTTPS with tokens or SSH keys, and richer GitHub API access using gh CLI or curl, choosing the optimal path based on available tools.

How does the automated detection flow choose between SSH and gh CLI for GitHub authentication?▼

The automated detection flow checks for installed tools like gh CLI, git, and curl, then selects the best GitHub authentication path based on environment capabilities, offering gh CLI for richer API access or SSH and HTTPS for standard git operations.

Can I use SSH keys instead of HTTPS tokens for GitHub authentication setup?▼

Yes, SSH keys are a supported authentication method alongside HTTPS with tokens, allowing you to establish reliable GitHub authentication for universal git operations across local, cloud, and container environments.

Why do I need to authenticate an agent to GitHub before performing PR actions and CI interactions?▼

Authenticating the agent to GitHub is required to perform repository operations, PR actions, and CI interactions without manual credential handling, ensuring reliable access across local, cloud, and container environments.