github-auth

Configure GitHub authentication for git operations and API access.

1|Updated May 16, 2026
One-click install
npx skills add https://github.com/devMoez/titan --skill github-auth-devmoez
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-auth
Source: https://github.com/devMoez/titan/tree/main/skills/github/github-auth
Command: npx skills add https://github.com/devMoez/titan --skill github-auth-devmoez

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

GitHub authentication setup is a common blocker when you want an agent to work with repositories, PRs, issues, and GitHub Actions without repeated login prompts or broken permissions.

Core Features & Use Cases

  • GitHub HTTPS token auth (recommended): Use a Personal Access Token to enable git operations and API access across repositories.
  • SSH key auth: Configure SSH keys and rewrite remotes so the agent can authenticate via SSH instead of passwords/tokens.
  • Optional gh CLI auth: If the GitHub CLI is installed, perform a browser or token-based login for richer GitHub API and git credential handling.
  • API fallback without gh: Use curl with a token when gh is not available, matching the approach used by other GitHub skills.

Quick Start

Tell the agent to set up GitHub authentication so git and GitHub API calls work, using a Personal Access Token for HTTPS on your machine.

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 operations and API access?

GitHub authentication can be set up for git and API access using a Personal Access Token over HTTPS, SSH keys, or the gh CLI. This configures stored credentials or environment variables to unblock repository and workflow automation.

Can I configure git credentials on a headless server without the gh CLI?

You can configure git credentials on headless servers without the gh CLI by using a Personal Access Token for HTTPS or SSH keys. The setup uses curl with a token for API access when gh is not installed.

What is the best way to authenticate GitHub API calls using a personal access token?

The best way to authenticate GitHub API calls with a personal access token is configuring HTTPS token auth. This enables both git operations and API access across repositories, using curl as a fallback if gh CLI is unavailable.

Does this GitHub auth setup support SSH key-based authentication for git remotes?

Yes, SSH key-based authentication is supported. It configures SSH keys and rewrites repository remotes so git operations authenticate via SSH instead of relying on passwords or personal access tokens.

Do I need specific token scopes for GitHub authentication to unblock pull request automation?

Specific token scopes are required for identity configuration to unblock pull request, issue, and workflow automation. The authentication setup provides requirements for personal access token scopes to ensure proper API permissions.

Why does GitHub authentication fail when switching between HTTPS and SSH remotes?

GitHub authentication fails during remote switches if credentials are not updated for the new protocol. The setup resolves this by applying SSH key configuration and rewriting remotes, or configuring HTTPS personal access tokens.