github-auth

Configure git and gh CLI authentication for GitHub access.

1|Updated Jun 25, 2026
One-click install
npx skills add https://github.com/Signmanal/VIGIL --skill github-auth-signmanal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-auth
Source: https://github.com/Signmanal/VIGIL/tree/main/skills/github/github-auth
Command: npx skills add https://github.com/Signmanal/VIGIL --skill github-auth-signmanal

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

The VIGIL security agent cannot interact with GitHub repositories, pull requests, issues, or CI/CD pipelines without valid authentication, creating a barrier to automated security operations, threat research, and workflow automation.

Core Features & Use Cases

  • Dual auth method support: Configure authentication via git (using HTTPS personal access tokens or SSH keys, no additional tools required) or the gh CLI (for streamlined GitHub API access and unified credential management).
  • Cross-environment compatibility: Works on Linux, macOS, and Windows, with tailored guidance for both interactive desktop sessions and headless server environments.
  • Use case: Security analysts can use this skill to quickly authenticate the VIGIL agent to organizational GitHub repositories, enabling automated security alert triage, vulnerability fix PR creation, and threat intelligence gathering from GitHub sources without repeated manual credential entry.

Quick Start

Use the github-auth skill to configure authentication so the VIGIL agent can access your GitHub repositories, pull requests, issues, and CI/CD 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 automated agent workflows?

GitHub authentication for automated agents is configured by setting up persistent credentials for git and gh CLI tools. This enables seamless automated access to repositories, pull requests, issues, and CI/CD pipelines without manual entry.

Can I use SSH keys instead of HTTPS personal access tokens for git authentication?

Yes, git authentication supports both HTTPS personal access tokens and SSH keys. This dual-method support allows you to choose your preferred credential type without requiring additional tools beyond git itself.

Does this GitHub credential management approach work on headless Linux servers?

Yes, the GitHub credential setup works on Linux, macOS, and Windows environments. It provides tailored guidance for both interactive desktop sessions and headless server deployments, ensuring broad cross-environment compatibility.

How can I authenticate to the GitHub API if the gh CLI tool is not installed?

If the gh CLI tool is unavailable, the skill provides fallback GitHub API access using curl. This ensures automated security operations and threat research can continue even without the gh CLI installed.

What's the best way to manage persistent GitHub credentials for security automation tasks?

The best approach for persistent credential management is using the gh CLI for unified access alongside git credential storage. This combination securely maintains long-term access for continuous security alert triage and automated vulnerability fix PR creation.

Why do I need to configure GitHub authentication before running automated security analysis?

GitHub authentication is required because security agents cannot interact with organizational repositories, pull requests, or CI/CD pipelines without valid credentials. Configuring access removes this barrier, enabling automated threat intelligence gathering and workflow automation.