github-auth

Configure GitHub authentication via git HTTPS tokens, SSH keys, or gh CLI.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/VYRE-Studios/Windows-Agentic-Framework --skill github-auth-vyre-studios
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-auth
Source: https://github.com/VYRE-Studios/Windows-Agentic-Framework/tree/main/skills/github/github-auth
Command: npx skills add https://github.com/VYRE-Studios/Windows-Agentic-Framework --skill github-auth-vyre-studios

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Enables an agent to securely authenticate with GitHub to manage repositories, pull requests, issues, and CI workflows without exposing credentials.

Core Features & Use Cases

  • Supports two authentication paths: git (HTTPS tokens or SSH keys) and gh (GitHub CLI) for API access and credential setup.
  • Automatic detection flow selects the best available method based on environment capabilities and current authentication status.
  • Practical use case: agent automates repo operations, PRs, and issue management with seamless authentication across diverse environments.

Quick Start

Choose a GitHub authentication method (git or gh) and follow the setup steps to configure credentials.

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?

GitHub authentication for agents is established by configuring credentials using either HTTPS tokens or SSH keys, or by setting up the GitHub CLI. The system automatically detects the best available method for your environment.

Should I use SSH keys or HTTPS tokens for git authentication in CI workflows?

Git authentication supports both SSH keys and HTTPS tokens for CI workflows. The system uses an automatic detection flow to select the best method based on your current environment capabilities and available credentials.

Do I need the GitHub CLI installed to manage pull requests and issues?

You do not strictly need the GitHub CLI to manage pull requests and issues, as basic git operations can use HTTPS or SSH. However, gh provides dedicated API access for advanced credential setup and management.

What dependencies are required to configure GitHub credentials securely?

Configuring GitHub credentials requires curl, git, and python3 to be installed in your environment. These dependencies support the dual-path authentication flow for both git and gh CLI methods.

How does credential storage work when automating repository operations?

Credential storage for automated repository operations is enforced by the system to ensure credentials are kept secure across environments. It provides guidance on token scopes and manages credentials without exposing them.

Why does my GitHub authentication fail across different environments?

GitHub authentication can fail across environments if credentials are not properly stored or if token scopes are insufficient. The dual-path flow detects current authentication status to securely operate across diverse setups.