How do I install the Github Authenticator skill?

Run npx skillmds@latest add aibot88/github-authenticator in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Github Authenticator safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Github Authenticator?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Github Authenticator free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Github Authenticator?

aibot88 (@aibot88) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Github Authenticator by aibot88 — Agent Skill

Name: Github Authenticator
Rating: 4.5 (4 reviews)
Author: aibot88

File contents

GitHub Authenticator

Instructions

When to Invoke This Skill

gh commands fail with authentication errors
User is setting up GitHub CLI for the first time
Need to verify current authentication status
Switching between GitHub accounts
Troubleshooting permission issues

Standard Workflow

Check Current Authentication Status
```
gh auth status
```
Interpret Output
- Logged in: Shows username, scopes, and token status
- Not logged in: Shows "You are not logged in to any GitHub hosts"
- Token expired: Shows authentication but with errors
Handle Authentication Issues

If not authenticated:
```
gh auth login
```
- Choose: GitHub.com or GitHub Enterprise
- Choose: HTTPS (recommended) or SSH
- Authenticate via: Browser (recommended) or Token
- Complete authentication flow
If token expired:
```
gh auth refresh
```
If wrong account:
```
gh auth logout
gh auth login
```

Required Scopes

Verify the token has necessary scopes:

repo - Full control of private repositories
workflow - Update GitHub Action workflows
admin:org - Read organization data (if working with org repos)

Error Scenarios

"HTTP 401: Bad credentials"

Token is invalid or expired
Run: gh auth refresh or re-authenticate

"HTTP 403: Resource not accessible"

Insufficient permissions
Check repository access
Verify organization membership

"HTTP 404: Not Found"

Repository doesn't exist
User doesn't have access
Check repository name and permissions

Configuration Check

View current configuration:

gh auth status --show-token

(Be careful - this displays the token)

Check which host is configured:

gh config get git_protocol

Set preferences:

gh config set git_protocol https
gh config set editor vim

Examples

Example 1: Authentication check before operations

Action: About to create PR
Step 1: Run gh auth status
Step 2: If authenticated, proceed with PR creation
Step 3: If not, guide user through gh auth login

Example 2: Authentication failure during operation

Error: "gh: HTTP 401: Bad credentials"
Action:
1. Inform user of authentication issue
2. Run gh auth status to diagnose
3. Guide through gh auth refresh or gh auth login
4. Retry original operation

Example 3: First-time setup

User: "Setup GitHub CLI"
Action:
1. Check if gh is installed: gh --version
2. Run gh auth login
3. Guide through authentication flow
4. Verify with gh auth status
5. Test with simple command: gh repo view

Example 4: Switching accounts

User: "I need to use my work GitHub account"
Action:
1. Show current account: gh auth status
2. Logout: gh auth logout
3. Login with work account: gh auth login
4. Verify: gh auth status

---name: github-authenticatordescription: Verify and troubleshoot GitHub CLI authentication. Use when gh commands fail with auth errors or when setting up GitHub integration for the first time.--- # GitHub Authenticator ## Instructions ### When to Invoke This Skill - `gh` commands fail with authentication errors - User is setting up GitHub CLI for the first time - Need to verify current authentication status - Switching between GitHub accounts - Troubleshooting permission issues ### Standard Workflow 1. **Check Current Authentication Status** ```bash gh auth status ``` 2. **Interpret Output** - **Logged in**: Shows username, scopes, and token status - **Not logged in**: Shows "You are not logged in to any GitHub hosts" - **Token expired**: Shows authentication but with errors 3. **Handle Authentication Issues** **If not authenticated:** ```bash gh auth login ``` - Choose: GitHub.com or GitHub Enterprise - Choose: HTTPS (recommended) or SSH - Authenticate via: Browser (recommended) or Token - Complete authentication flow **If token expired:** ```bash gh auth refresh ``` **If wrong account:** ```bash gh auth logout gh auth login ``` ### Required Scopes Verify the token has necessary scopes: - `repo` - Full control of private repositories - `workflow` - Update GitHub Action workflows - `admin:org` - Read organization data (if working with org repos) ### Error Scenarios **"HTTP 401: Bad credentials"** - Token is invalid or expired - Run: `gh auth refresh` or re-authenticate **"HTTP 403: Resource not accessible"** - Insufficient permissions - Check repository access - Verify organization membership **"HTTP 404: Not Found"** - Repository doesn't exist - User doesn't have access - Check repository name and permissions ### Configuration Check **View current configuration:** ```bash gh auth status --show-token ``` (Be careful - this displays the token) **Check which host is configured:** ```bash gh config get git_protocol ``` **Set preferences:** ```bash gh config set git_protocol https gh config set editor vim ``` ## Examples ### Example 1: Authentication check before operations ``` Action: About to create PR Step 1: Run gh auth status Step 2: If authenticated, proceed with PR creation Step 3: If not, guide user through gh auth login ``` ### Example 2: Authentication failure during operation ``` Error: "gh: HTTP 401: Bad credentials" Action: 1. Inform user of authentication issue 2. Run gh auth status to diagnose 3. Guide through gh auth refresh or gh auth login 4. Retry original operation ``` ### Example 3: First-time setup ``` User: "Setup GitHub CLI" Action: 1. Check if gh is installed: gh --version 2. Run gh auth login 3. Guide through authentication flow 4. Verify with gh auth status 5. Test with simple command: gh repo view ``` ### Example 4: Switching accounts ``` User: "I need to use my work GitHub account" Action: 1. Show current account: gh auth status 2. Logout: gh auth logout 3. Login with work account: gh auth login 4. Verify: gh auth status ```

Frequently asked questions

Github Authenticator