agentleFS
Sign inStart free
tumftumf/skills/gogcli/SKILL.md

gogcli

Skill4 starsChanged 7 months agoMITView on GitHub

Fast, script-friendly CLI for Google services via `gog`. Use this skill whenever the user needs to work with Gmail, Google Calendar, Drive, Docs, Sheets, Slides, Forms, Apps Script, Contacts, Tasks, People, Chat, Classroom, Groups, Admin, or Keep from the terminal, especially for Google Workspace automation, account setup, OAuth/client configuration, service accounts, domain-wide delegation, or JSON/scriptable workflows. Prefer this skill even when the user does not mention `gog` explicitly but is clearly trying to automate or inspect Google services from a CLI or agent workflow.

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 4 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Default output is human-readable.

    line 71
  2. Very specific:

    Use --json for machine-readable scripting.

    line 72
  3. Very specific:

    Use --plain for stable TSV-like output.

    line 73
  4. Distinctive:

    Prefer read-only discovery before mutating commands.

    line 75
  5. Very specific:

    Use --json whenever downstream parsing matters.

    line 93
  6. Distinctive:

    Prefer the smallest scope set that can accomplish the task.

    line 94
  7. Distinctive:

    Do not assume consumer Gmail accounts can use Chat, Admin, Groups, or Keep service-account flows.

    line 97

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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

gogcli - Google in your terminal

Overview

gog is a script-friendly CLI for Google services with JSON-first output, multiple accounts, and flexible authentication. This skill is for agents that need to inspect or automate Google Workspace and Gmail workflows safely.

Core areas:

  • Gmail: search, read, send, drafts, labels, filters, watch webhooks, tracking
  • Calendar: events, invites, team calendars, free/busy, conflicts, special event types
  • Drive: list/search/upload/download/share/move/delete, shared drives
  • Docs / Slides / Sheets: create, copy, export, update, formatting helpers
  • Contacts / People / Tasks
  • Chat, Classroom, Forms, Apps Script
  • Groups, Admin, Keep in Workspace environments

Installation

See references/installation.md.

Authentication Quick Start

For first-time setup, see references/oauth.md and references/apis.md.

Minimal happy path:

gog auth credentials ~/Downloads/client_secret_*.json
gog auth add you@gmail.com

gog auth list
export GOG_ACCOUNT=you@gmail.com
gog auth status
gog gmail labels list

gog auth status only shows the current/selected account context. To confirm which accounts are authenticated at all, check gog auth list.

Authentication Model

gog supports:

  • Multiple accounts via --account / GOG_ACCOUNT
  • Account aliases via gog auth alias ...
  • Multiple OAuth clients via --client / GOG_CLIENT
  • Keyring backends: auto, keychain, file
  • Least-privilege auth with --readonly, --drive-scope, --gmail-scope
  • Workspace service accounts with domain-wide delegation

See details in references/oauth.md.

Workspace service accounts

For Workspace-only flows such as Keep or Admin, verify service-account configuration before acting.

Quick check:

gog --account you@yourdomain.com auth status

See full setup in references/oauth.md.

Output and automation conventions

  • Default output is human-readable.
  • Use --json for machine-readable scripting.
  • Use --plain for stable TSV-like output.
  • Human hints/progress go to stderr.
  • Prefer read-only discovery before mutating commands.

Recommended preflight pattern:

gog auth status --json
gog gmail labels list --json
gog calendar calendars --json
gog drive ls --max 5 --json

Common command patterns

See references/commands.md.

Agent guidance

  • First confirm the target account with gog auth status or explicit --account.
  • Use --json whenever downstream parsing matters.
  • Prefer the smallest scope set that can accomplish the task.
  • For Workspace-only commands, verify service-account/domain-wide-delegation status first.
  • For Gmail watch/tracking flows, verify external webhook URLs and auth before enabling writes.
  • Do not assume consumer Gmail accounts can use Chat, Admin, Groups, or Keep service-account flows.

References

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.

Reviews can't be read right now.

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