Github auth
Skill Martin-Hausleitner/martins-awesome-skills/skills/github/github-auth
Martin's Awesome Skills: public-safe Hermes and OpenClaw agent skills with Telegram approval workflows
npx -y skills add Martin-Hausleitner/martins-awesome-skills --skill github-authAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use when GitHub authentication is missing, broken, or needed before repository, issue, pull request, or CI work
SKILL.md
1.1 KB, as published. Nobody here has run it
GitHub Auth
Overview
Choose the least surprising GitHub auth path for the current machine, then verify it before doing repository work.
Workflow
- Check what is installed:
git --version
gh --version 2>/dev/null || true
gh auth status 2>/dev/null || true
- Prefer an already-authenticated
ghsession when available. - If
ghis not authenticated, ask the user to completegh auth login. - If
ghis unavailable, use normalgitcredentials or SSH. - Configure commit identity only when needed:
git config --global user.name "Your Name"
git config --global user.email "[email protected]"
- Verify with a read-only command before pushing:
git ls-remote origin
Safety
- Never paste tokens into committed files.
- Prefer credential helpers or
gh auth loginover token-in-remote URLs. - Do not print full secrets in summaries, logs, screenshots, or pull requests.