skills.rest
agentic-in
agentic-inOFFICIAL
Explore all skills by this author →
WebsiteGitHub

GitHub Auth

Diagnose GitHub authentication status and identify permission blockers.

577|62|Updated May 15, 2026
Search Tags:#github#permissions#repository#gh#identity#auth#token
One-click install
npx skills add https://github.com/agentic-in/elephant-agent --skill github-auth-agentic-in
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: GitHub Auth
Source: https://github.com/agentic-in/elephant-agent/tree/main/packages/skills/builtin_packages/github/github-auth
Command: npx skills add https://github.com/agentic-in/elephant-agent --skill github-auth-agentic-in

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps diagnose and verify GitHub authentication, identify the active identity, and debug missing permissions before performing GitHub operations.

Core Features & Use Cases

  • Verify current authentication status using the GitHub CLI or a GitHub connector.
  • Identify whether the blocker is missing tokens, wrong account, or insufficient repository permissions.
  • Provide guidance to re-authenticate or re-run actions after access is fixed.

Quick Start

Check my GitHub authentication status and confirm the active identity and necessary permissions before running a GitHub action.

Frequently Asked Questions about GitHub Auth

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check my GitHub authentication status and active identity?▼

To check GitHub authentication status, use the GitHub CLI or a connector to verify your active identity and token scopes, ensuring credentials are valid before performing operations.

Why do my GitHub actions fail with permission errors in CI workflows?▼

GitHub actions fail due to missing tokens, wrong active account, or insufficient repository permissions. Diagnosing the GitHub auth status identifies the specific blocker type causing the failure.

How to diagnose insufficient repository permissions before running a GitHub action?▼

Diagnose insufficient repository permissions by integrating the GitHub CLI or connector to check active identity and token scopes, reporting the exact blocker type before executing the action.

Can I verify GitHub token scopes using the GitHub CLI?▼

Yes, you can verify GitHub token scopes using the GitHub CLI. The authentication check identifies whether missing tokens or wrong accounts are blocking repository access and operations.

What should I do after fixing a GitHub authentication blocker?▼

After fixing a GitHub authentication blocker like a missing token or wrong account, re-authenticate your credentials and re-run the blocked GitHub actions or manual operations to proceed.

Does this GitHub auth diagnosis work with both manual actions and CI workflows?▼

Yes, GitHub auth diagnosis works across both CI workflows and manual actions. It verifies identity and repository permissions regardless of how the GitHub operations were triggered.

Related Skills

Explore More Software Engineering Skills→
Dq666dingerDq666dinger
1

github-auth

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

Community
Advanced
luongldptitluongldptit

terminal-ops

Enforce evidence-first terminal workflows for repository execution tasks.

Community
Advanced
KrishpotanwarKrishpotanwar

github-workflow-automation

Automate GitHub repository management and CI/CD pipelines across multiple repositories.

Community
Advanced
FenixAllianceFenixAlliance

absuite-identity

Manage user identity, OAuth flows, and OpenID Connect configurations via the Alliance Business Suite REST API.

Official
Intermediate