agentleFS
Sign inStart free
Martin-HausleitnerMartin-Hausleitner/martins-awesome-skills/skills/github/github-auth/SKILL.md

github-auth

Skill3 starsChanged 6 months agoMITView on GitHub

Use when GitHub authentication is missing, broken, or needed before repository, issue, pull request, or CI work

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

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

  • 0

    Common

    Most of the 19 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Check what is installed:

    line 14
  2. Very specific:

    Prefer an already-authenticated gh session when available.

    line 22
  3. Very specific:

    If gh is not authenticated, ask the user to complete gh auth login.

    line 23
  4. Very specific:

    If gh is unavailable, use normal git credentials or SSH.

    line 24
  5. Distinctive:

    Verify with a read-only command before pushing:

    line 32
  6. Distinctive:

    Never paste tokens into committed files.

    line 40
  7. Very specific:

    Prefer credential helpers or gh auth login over token-in-remote URLs.

    line 41
  8. Distinctive:

    Do not print full secrets in summaries, logs, screenshots, or pull requests.

    line 42

“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 Auth

Overview

Choose the least surprising GitHub auth path for the current machine, then verify it before doing repository work.

Workflow

  1. Check what is installed:
git --version
gh --version 2>/dev/null || true
gh auth status 2>/dev/null || true
  1. Prefer an already-authenticated gh session when available.
  2. If gh is not authenticated, ask the user to complete gh auth login.
  3. If gh is unavailable, use normal git credentials or SSH.
  4. Configure commit identity only when needed:
git config --global user.name "Your Name"
git config --global user.email "you@example.com"
  1. 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 login over token-in-remote URLs.
  • Do not print full secrets in summaries, logs, screenshots, or pull requests.

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