Agent skill · Security

github-auth

GitHub auth setup: HTTPS tokens, SSH keys, gh CLI.

HezaoHezaogithub.com/HezaoHezaoGitHub ↗
claude-codecan modify filesMIT
Install
npx skills add HezaoHezao/poirot --skill github-auth --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 4 KB
Bundled scripts: none
Declared author: Adapted from hermes-agent (Nous Research, MIT)
Allowed tools: -bash
Path: poirot/backend/agents/skill/builtin_skills/software-development/github-auth/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 139
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# GitHub Authentication Setup Sets up authentication so the agent can work with GitHub repositories, PRs, issues, and CI. ## Detection Flow When a user asks to work with GitHub, run this check first: ```bash git --version gh --version 2>/dev/null || echo "gh not installed" 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:** 1. If `gh auth status` shows authenticated → use `gh` for everything 2. If `gh` installed but not authenticated → use "gh auth" method 3. If `gh` not installed → use "git-only" method ## Method 1: Git-Only (No gh) ### HTTPS with Personal Access Token (Recommended) **Step 1: Create a token** at https://github.com/settings/tokens (classic) or https://github.com/settings/personal-access-tokens (fine-grained). Scope: `repo`, `workflow`, `read:org`. **Step 2: Configure git credential helper:** ```bash # Store credentials (plaintext, dev machine only) git config --global credential.helper store # Or use a credential cache (timed, more secure) git config --global credential.helper 'cache --timeout=3600' ``` **Step 3: First push triggers prompt:** ```bash #

What's inside
Steps it walks through
  1. Detection Flow
  2. Method 1: Git-Only (No gh)
  3. HTTPS with Personal Access Token (Recommended)
  4. SSH Keys
  5. Method 2: gh CLI
  6. Verification
  7. Common Auth Setup Block
  8. Pitfalls
Commands it runs
git --version
gh --version 2>/dev/null || echo "gh not installed"
gh auth status 2>/dev/null || echo "gh not authenticated"
git config --global credential.helper 2>/dev/null || echo "no git credential helper"
Store credentials (plaintext, dev machine only)
git config --global credential.helper store
Or use a credential cache (timed, more secure)
git config --global credential.helper 'cache --timeout=3600'
git push origin main
export GITHUB_TOKEN="ghp_xxxxxxxxxxxx"
More from poirot
All skills →
About this skill
What does the github-auth skill do?

GitHub auth setup: HTTPS tokens, SSH keys, gh CLI.

How do I install it?

Run `npx skills add HezaoHezao/poirot --skill github-auth --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From HezaoHezao/poirot, a repository with 139 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going