github-auth

Configure and verify GitHub authentication via git or gh CLI.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

GitHub authentication setup enables the agent to access repositories, pull requests, issues, and CI workflows securely and without friction.

Core Features & Use Cases

  • GitHub authentication methods: supports git HTTPS with tokens or SSH keys, and gh CLI-based authentication for richer API access.
  • Automatic detection: detects available tools and picks the best method automatically.
  • Use Case: when provisioning an OWLS agent on a new host, run the setup to authenticate for repo access and actions.

Quick Start

Configure GitHub authentication by choosing git or gh, then verify access with gh auth status or git ls-remote.

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?

Set up GitHub authentication by providing a token or SSH key to configure access. The flow detects available tools like git or gh CLI, automatically picks the best method, and verifies access to repositories and workflows.

What is the best way to authenticate to GitHub using git or gh CLI?

The best way to authenticate is letting the system detect whether git or gh CLI is installed and authenticated. It configures git HTTPS with tokens, SSH keys, or gh CLI authentication to provide optimal API access for your agent.

Do I need the gh CLI installed to configure GitHub credentials?

No, the gh CLI is optional for configuring GitHub credentials. The setup requires git and can use HTTPS with tokens or SSH keys, but it will utilize gh CLI for richer API access if it is installed and authenticated.

How does automatic detection work for GitHub SSH and token authentication?

Automatic detection checks for installed tools and existing credentials like SSH keys or tokens. Based on what is available, it selects the optimal authentication method, configuring either git HTTPS, SSH, or gh CLI for secure repository access.

Can I verify GitHub authentication access for repositories and PRs without manual checks?

You can verify GitHub authentication automatically through the setup flow. After configuring credentials, it validates access to repositories, pull requests, issues, and CI workflows using commands like gh auth status or git ls-remote.

Why does my agent need GitHub authentication configured on a new host?

GitHub authentication is required on a new host to securely access repositories, pull requests, issues, and CI workflows without friction. Running the setup provisions the agent with the necessary credentials to operate independently.