google-signin SKILL.md skillA
google-signin from ssheleg/sheleg-dev is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add ssheleg/sheleg-dev/google-signin@git:20261020.6a7c3e1Pins git:20261020.6a7c3e1 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- ssheleg/sheleg-dev
- Path
plugins/sheleg-dev/skills/google-signin/SKILL.md- Versions recorded
- 6
- Latest version
- git:20261020.6a7c3e1, committed Oct 20, 2026
- First version recorded
- Aug 31, 2026
- Size
- 9,766 bytes
- Repository stars
- 4
- License
- MIT
Use when implementing or debugging Google sign-in on a website: the GIS button or One Tap, server-side ID token checks, linking Google to password accounts, login CSRF. Not for a server authenticating to Google (google-auth). Opt out: no wiring, без обвязки. Triggers - "sign in with google", "google login", "GIS", "one tap", "account linking", "вход через Google", "связать аккаунты".
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Google Sign-In (GIS) — production web login
Condensed operating instructions. Full narrative guide with diagrams, token
anatomy, troubleshooting table, and a copy-paste FastAPI + JS skeleton:
[references/full-guide.md](references/full-guide.md) — read it when
implementing from scratch; its FastAPI + JS skeleton is the reference
implementation this skill ships.
## Pick the right flow first
- Only need "who is this user?" → **GIS ID-token flow** (this skill): load
`https://accounts.google.com/gsi/client`, receive one Google-signed JWT,
verify server-side. No redirect URI, no client secret, no Google-token
storage.
- Need to call Google APIs (Gmail/Drive/Calendar) on the user's behalf →
OAuth 2.0 **authorization-code** flow instead (redirect URI + client
secret + refresh tokens). Never use the code flow just for login.
## Core flow (ID-token)
1. Frontend: fetch a **server-issued nonce** first (`GET /api/auth/google/nonce`
— the server stores it with a TTL, bound to a pre-auth HttpOnly cookie),
then `google.accounts.id.initialize({ client_id, callback, nonce })`
+ `renderButton()`. A client-generated nonce POSTed back proves nothing:
…Read the whole file at its exact version.
How to install
mdr add ssheleg/sheleg-dev/google-signin@sha256:a2c276c7ba101c87The line at the top of this page pins the label git:20261020.6a7c3e1, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_m24dff4geov5hiz2)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 6 versions of this file, between Aug 31, 2026 and Oct 20, 2026, about one every 10 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261020.6a7c3e1 latest | 2026-10-20 | 6a7c3e1 | 9,766 B | A | view · diff |
| git:20261013.9703d5e | 2026-10-13 | 9703d5e | 9,945 B | A | view · diff |
| git:20260914.ca2da3a | 2026-09-14 | ca2da3a | 9,609 B | A | view · diff |
| git:20260909.ebab4a1 | 2026-09-09 | ebab4a1 | 9,136 B | A | view · diff |
| git:20260906.e7d6e89 | 2026-09-06 | e7d6e89 | 6,775 B | A | view · diff |
| git:20260831.9627bcc | 2026-08-31 | 9627bcc | 6,762 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (9766 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
ssheleg/sheleg-dev · 4 stars · license MIT · pushed 2026-10-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_m24dff4geov5hiz2 GET https://markdownregistry.com/api/v1/resolve?ref=ssheleg/sheleg-dev/google-signin GET https://markdownregistry.com/api/v1/blob/a2c276c7ba101c87fd8e98c88784ceac905f8facd08540965f5c7795135d738f
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.