agentleFS
Sign inStart free
rakaarwakyrakaarwaky/agents-arwaky/skills/git/github-auth/SKILL.md

github-auth

Skill0 starsChanged 3 days agoMITView on GitHub

GitHub auth setup: HTTPS tokens, SSH keys, gh CLI login (browser and device flow).

19 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 0 are distinctive, and 5 are very specific to this project.

  • 0

    Common

    Most of the 19 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Detection first: Run git --version, gh --version, gh auth status, and git config --global credential.helper before choosing a path.

    line 19
  2. Very specific:

    gh authenticated: If gh auth status shows authenticated → use gh for everything.

    line 20
  3. Very specific:

    gh not authenticated: If gh is installed but not authenticated → use the gh auth method (browser or device flow).

    line 21
  4. Very specific:

    gh not installed: If gh is not installed → use the git-only method (no sudo needed).

    line 22
  5. Very specific:

    git identity: Always configure user.name and user.email.

    line 24

“Common” is measured: kept by at least 6 in 10 of the 19 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

GitHub Authentication Setup

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 keys
  • gh CLI (if installed) — richer GitHub API access with a simpler auth flow

Global Rules

Rules that apply to both auth paths. Detection and method files cite these; they never restate them.

  • Detection first: Run git --version, gh --version, gh auth status, and git config --global credential.helper before choosing a path.
  • gh authenticated: If gh auth status shows authenticated → use gh for everything.
  • gh not authenticated: If gh is installed but not authenticated → use the gh auth method (browser or device flow).
  • gh not installed: If gh is not installed → use the git-only method (no sudo needed).
  • Token scopes: For HTTPS, create a personal access token with repo, workflow, and read:org scopes (90-day expiration recommended).
  • git identity: Always configure user.name and user.email; required for commits.

Routing

StepReferencePurpose
Step 0references/step-0-detect.mdCheck git, gh, gh auth status, credential helper; choose git-only or gh-cli path.
Step 1references/step-1-gh-cli-auth.mdgh login methods: browser, device flow, hosts.yml fallback.
Step 2references/step-2-git-only-auth.mdHTTPS with personal access token or SSH key: full setup steps for both.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free