Gmail OAuth Setup

PassAudited by ClawScan on May 10, 2026.

Overview

This skill transparently helps set up Gmail OAuth for the gog CLI, but users should understand it grants persistent Gmail account access.

Before installing, make sure you trust the gog CLI source, use a Google Cloud OAuth client you created, review the requested Gmail scope, and understand that a refresh token will be stored for ongoing Gmail access. Use a narrower scope such as gmail.readonly when possible and revoke the token later if access is no longer needed.

Findings (3)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

Note

ASI03: Identity and Privilege Abuse

What this means

If authorized, gog can access the selected Gmail account with read, send, delete, and label-management permissions until the token is revoked.

Why it was flagged

The helper requests Gmail modify access and imports a refresh token into gog, creating persistent delegated Gmail access.

Skill content

SCOPE="https://www.googleapis.com/auth/gmail.modify" ... "refresh_token": "${refresh_token}" ... gog auth tokens import "$token_file"

Recommendation

Use the least-privileged Gmail scope that works for your use case, authorize only accounts you intend to connect, and revoke the token from your Google Account if you no longer need it.

Note

ASI04: Agentic Supply Chain Vulnerabilities

What this means

The OAuth flow relies on the behavior and security of the installed gog CLI.

Why it was flagged

The skill depends on an external CLI installed outside the skill package; this is disclosed, but users must trust that dependency and source.

Skill content

`gog` CLI installed (`brew install steipete/tap/gogcli`)

Recommendation

Install gog only from a trusted source, verify the project and package before use, and keep it updated.

Note

ASI09: Human-Agent Trust Exploitation

What this means

A user who proceeds with the wrong OAuth app could grant Gmail access to an untrusted Google Cloud project.

Why it was flagged

The instructions tell users how to proceed past Google's warning; this is reasonable for a personal OAuth app but should not be followed for an app the user does not control.

Skill content

"Google hasn't verified this app" ... "Go to [app name] (unsafe)" ... "Safe to proceed since you own the app."

Recommendation

Only bypass the warning when you created and control the Google Cloud OAuth client and have verified the app name, client, and requested scopes.