agentleFS
IgorGanapolskyIgorGanapolsky/mac-yolo-safeguards/.agents/skills/gitbutler-google-sso/SKILL.md

gitbutler-google-sso

Skill3 starsChanged 4 days agoMITView on GitHub

HARD GitButler Cloud login is Google SSO (personal Gmail via /igor-login-accounts; never GitHub for the GitButler Cloud account). BrowserOS neo first. Do not hijack daily Chrome. Do not print the access token. Do not click Refresh token (logs out everywhere). Trigger: GitButler login, app.gitbutler.com, gitbutler.com/profile, but cloud auth. Slash: /gitbutler-google-sso.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    If login wall: Sign in with Google → choose the personal Gmail from /igor-login-accounts

    line 68
  2. Distinctive:

    Stop when profile email matches that Gmail and Log out is visible

    line 70
  3. Distinctive:

    Do not click Refresh token (logs the desktop app out everywhere)

    line 71
  4. Very specific:

    Do not paste the access token into chat, git, vault, skill bodies, or security -w argv

    line 72
  5. Distinctive:

    NEVER click Refresh token

    line 85

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “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

GitButler Cloud — Google SSO

Cloud login: https://app.gitbutler.com/ → Sign in with Google Profile: https://gitbutler.com/profile

Identity: personal Gmail from /igor-login-accounts. Never GitHub for the GitButler Cloud account.

GitHub forge OAuth (but config forge / IgorGanapolsky) is a different login. GitButler Cloud identity is Google.

Proof of a live session

Web Cloud (Google SSO) — GET https://app.gitbutler.com/api/login/whoami with X-Auth-Token from Keychain, HTTP 200:

  • email matches /igor-login-accounts Google SSO
  • email_verified true
  • picture host lh3.googleusercontent.com (Google SSO, not GitHub)
  • Profile page shows that Gmail plus Log out (do not click Refresh token)

Desktop cache is not login. ~/Library/Application Support/com.gitbutler.app/user.json stores profile fields only (access_token is skip_serializing). GitButler itself says: if gitbutler_access_token is missing from Keychain, "login is now invalid."

CLI/desktop Cloud token: Keychain generic passwords, presence-only (find-generic-password, never -w in chat):

serviceaccount
gitbutler_access_tokenpersonal Gmail (/igor-login-accounts)
release-gitbutler_access_tokenGitButler (GitButler keyring-rs BuildKind, CHANNEL=release)

Whoami (pipe only; never print the token):

security find-generic-password -s gitbutler_access_token -w \
  | python3 -c 'import sys,json,urllib.request; t=sys.stdin.read().strip();
req=urllib.request.Request("https://app.gitbutler.com/api/login/whoami", headers={"X-Auth-Token": t});
b=json.load(urllib.request.urlopen(req, timeout=20));
print("verified" if b.get("email_verified") else "unverified", "id", b.get("id"))'

Forge (separate from Cloud SSO): but config forge → GitHub OAuth IgorGanapolsky.

Examples (show, don't tell)

Weak: Log into GitButler with GitHub.

Gold:

$ security find-generic-password -s gitbutler_access_token -w \
  | python3 -c 'import sys,json,urllib.request; t=sys.stdin.read().strip();
req=urllib.request.Request("https://app.gitbutler.com/api/login/whoami", headers={"X-Auth-Token": t});
b=json.load(urllib.request.urlopen(req, timeout=20));
print("verified" if b.get("email_verified") else "unverified")'

Login procedure

  1. BrowserOS neo own tab: https://app.gitbutler.com/
  2. If login wall: Sign in with Google → choose the personal Gmail from /igor-login-accounts
  3. Password only if Google challenges: Keychain google.com — never print
  4. Stop when profile email matches that Gmail and Log out is visible
  5. Do not click Refresh token (logs the desktop app out everywhere)
  6. Do not paste the access token into chat, git, vault, skill bodies, or security -w argv

Token helper (local, not in this public repo): ~/.grok/skills/gitbutler-google-sso/scripts/store_cloud_token.py.

Fleet wall

Still never but setup on mac-yolo-safeguards / ThumbGate / RealEstate shared trees. Overlay: [[gitbutler-fleet-safe]] / Codex #2119 gitbutler-route.

Rubric

  • whoami prints verified/id only — never the token
  • Cloud identity is Google SSO (/igor-login-accounts), forge is GitHub IgorGanapolsky
  • doctor_exit=0 (Keychain token present, not printed)
  • NEVER click Refresh token

Related

  • [[gitbutler-fleet-automations]]
  • [[igor-login-accounts]]
  • Official but skill: ~/.grok/skills/gitbutler

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.