Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →lord1egypt/github-auth
GitHub auth setup: HTTPS tokens, SSH keys, gh CLI login.
Passed 21 of 22 test cases with the skill, and 20 of 22 without it.
2 fixed19 passed either way0 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
My automated scripts on a headless Linux server are throwing permission errors when trying to connect to GitHub. Can you help me diagnose my current authentication state and establish a working configuration for both standard Git operations and command-line API requests?
| Checked | Without skill | With skill |
|---|---|---|
| Recommends running git --version to check Git installation. | Missed | Passed |
| Recommends running gh auth status to inspect GitHub CLI auth state. | Passed | Passed |
The instructions your model reads when the skill loads.
This skill sets up authentication so the agent can work with GitHub repositories, PRs, issues, and CI. It covers two paths:
git (always available) — uses HTTPS personal access tokens or SSH keysgh CLI (if installed) — richer GitHub API access with a simpler auth flowWhen a user asks you to work with GitHub, run this check first:
# Check what's available
git --version
gh --version 2>/dev/null || echo "gh not installed"
# Check if already authenticated
gh auth status 2>/dev/null || echo "gh not authenticated"
git config --global credential.helper 2>/dev/null || echo "no git credential helper"
Decision tree:
gh auth status shows authenticated → you're good, use gh for everythinggh is installed but not authenticated → use "gh auth" method belowgh is not installed → use "git-only" method below (no sudo needed)This works on any machine with git installed. No root access needed.
This is the most portable method — works everywhere, no SSH config needed.
Step 1: Create a personal access token
Tell the user to go to: https://github.com/settings/tokens
test cases passed, vs 20 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.