auth-user

Identify authenticated GitHub CLI and Git user accounts and credential methods.

3|1|Updated Dec 3, 2025
One-click install
npx skills add https://github.com/nsheaps/ai-mktpl --skill auth-user
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: auth-user
Source: https://github.com/nsheaps/ai-mktpl/tree/main/plugins/scm-utils/skills/auth-user
Command: npx skills add https://github.com/nsheaps/ai-mktpl --skill auth-user

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill identifies which user account and credential method are currently configured for GitHub CLI and Git operations, helping developers troubleshoot authentication failures, account confusion, and credential mismatches.

Core Features & Use Cases

  • GitHub CLI status: Reports the active gh account, token presence, configured git protocol, and token scopes.
  • HTTPS credential inspection: Uses git credential fill to show stored usernames and helper-backed credentials for hosts.
  • SSH verification: Tests SSH connectivity to determine which account an SSH key belongs to and displays verbose connection details when needed.
  • Use Case: Ideal for developers switching between personal and work accounts, debugging CI authentication, or confirming which credentials will be used for git operations.

Quick Start

Ask the skill to check gh auth status, inspect HTTPS credentials, and test SSH to summarize authenticated usernames and methods.

Frequently Asked Questions about auth-user

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

FAQPage Schema
How do I check which GitHub account my git commands are using?

Git credential mismatches occur when stored HTTPS credentials conflict with active SSH keys. Inspecting git credential fill output and testing SSH connectivity reveals which stored username or key is actively authenticating your git operations.

What is the best way to troubleshoot git authentication failures in a multi-account setup?

Troubleshooting git authentication in a multi-account setup requires verifying gh auth status, HTTPS credential storage, and SSH key ownership. This identifies the exact active user account and credential method causing authentication failures or account confusion.

Can I verify which SSH key my GitHub CLI is using to connect?

You can verify which SSH key your GitHub CLI is using by testing SSH connectivity to GitHub. This tests the active SSH connection, determines which account the key belongs to, and displays verbose connection details for verification.

Does checking git credential fill expose my stored HTTPS usernames and tokens?

Checking git credential fill exposes stored usernames and helper-backed credentials for configured hosts. It reveals the active HTTPS credential storage mechanism and username, helping you identify credential mismatches without exposing complete raw token values.

Why does my CI system fail GitHub authentication when a local token works?

CI system GitHub authentication failures happen when environment tokens differ from local configurations. Inspecting gh auth status, environment token visibility, and git protocol settings identifies the credential method mismatch causing the pipeline failure.