github-auth

Configure GitHub authentication for automated agents using tokens, SSH keys, or gh CLI.

Updated Jun 19, 2026
One-click install
npx skills add https://github.com/AnandaAnugrahHandyanto/savarez_agent --skill github-auth-anandaanugrahhandyanto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-auth
Source: https://github.com/AnandaAnugrahHandyanto/savarez_agent/tree/main/skills/github/github-auth
Command: npx skills add https://github.com/AnandaAnugrahHandyanto/savarez_agent --skill github-auth-anandaanugrahhandyanto

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

The agent needs reliable and secure GitHub authentication to operate with repositories, PRs, issues, and CI workflows across environments, eliminating manual credential handling.

Core Features & Use Cases

  • Git-only authentication supports HTTPS personal access tokens or SSH keys, with credential storage and painless re-authentication.
  • gh CLI authentication provides API access and git credentials in one flow, including interactive and token-based methods.
  • Use cases include cloning, pushing, creating PRs, and triggering GitHub Actions from autonomous agents.

Quick Start

Configure authentication for GitHub by selecting a method and following prompts to store credentials and set your identity.

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 agents?

Set up GitHub authentication by selecting token-based, SSH-based, or gh CLI methods, following prompts to securely store credentials and configure your git identity for autonomous agent access.

What's the best way to authenticate an autonomous agent to access GitHub repositories and PRs?

Authenticating autonomous agents to access GitHub repositories and PRs is best handled via gh CLI, which provides API access and git credentials in one flow, or via HTTPS tokens and SSH keys.

Can I use SSH keys instead of a personal access token for GitHub authentication in CI workflows?

Yes, you can use SSH keys instead of a personal access token for GitHub authentication in CI workflows. The system supports both git-only SSH key and HTTPS token credential storage methods.

Does GitHub authentication require gh CLI to be installed, or can I use git directly?

GitHub authentication does not strictly require gh CLI. The system automatically detects available tools and supports git-only flows using HTTPS tokens or SSH keys if gh CLI is absent.

Why does my agent need to detect existing credentials before configuring GitHub access?

Detecting existing credentials before configuring GitHub access prevents overwriting valid authentication. The system checks gh status and current SSH keys or tokens to provide appropriate end-to-end options.

Do I need to configure a git identity separately when setting up GitHub token authentication?

Configuring a git identity is an optional step when setting up GitHub token authentication. The process allows you to simultaneously store credentials and set your git identity during the setup flow.