New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Google Workspace CLI

by LeoYeAI in LeoYeAI/openclaw-master-skills

Installs and authenticates the gws CLI, then automates Gmail, Drive, Sheets, Calendar, Docs, Chat and Tasks with ready-made recipes, persona bundles and security audits.

MITAuto-check: notesProductivity & Automation

Install Google Workspace CLI

skills CLI
$ npx skills add LeoYeAI/openclaw-master-skills --skill google-workspace-cli -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install LeoYeAI/openclaw-master-skills google-workspace-cli --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/cs-google-workspace-cli .claude/skills/google-workspace-cli && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
google-workspace-cli
GitHub stars
2.2k
Token cost
~2.6k tokens
SKILL.md length
534 words
Files
12 (incl. scripts, references, assets)
Skills in repo
1,215
Repo updated
First seen
Licence
MIT

At a glance

Installs and authenticates the gws CLI, then automates Gmail, Drive, Sheets, Calendar, Docs, Chat and Tasks with ready-made recipes, persona bundles and security audits.

  • Works in 5 steps: Use OAuth with minimal scopes — request… → Store tokens in the system keyring,… → Rotate service account keys every 90 days → …
  • Setting up and authenticating the gws CLI for a Google Workspace account
  • SKILL.md covers Quick Start, Installation, Authentication and Workflow 1: Gmail Automation, plus 3 more sections
  • Runs Python scripts from its folder; calls python3, npm and cargo; needs GWS_SERVICE_ACCOUNT_KEY and GWS_CLIENT_SECRET

What it does

This skill guides the agent through administering Google Workspace with the open-source gws command-line tool. It covers installing gws through npm, Cargo or a pre-built binary, and signing in with an interactive OAuth flow or with a service account for headless and CI use. Environment variables such as GWS_CLIENT_ID, GWS_SERVICE_ACCOUNT_KEY and GWS_DELEGATED_USER control credentials, token location and the default output format.

Workflows are organized by service, starting with Gmail: sending and replying, searching, labels and filters. Bundled Python scripts check the setup (gws_doctor.py), guide authentication (auth_setup_guide.py), run recipes (gws_recipe_runner.py), reshape command output into tables (output_analyzer.py) and audit the workspace (workspace_audit.py). The skill refers to 43 built-in recipes and 10 persona bundles for role-based work, with reference files for commands, a recipes cookbook and troubleshooting.

When your agent uses it

  • Setting up and authenticating the gws CLI for a Google Workspace account
  • Automating Gmail sending, search, labels or filters from the command line
  • Listing or managing Drive files and Calendar events in bulk
  • Running a security audit of a Google Workspace account

Example prompts

  • “Check that gws is installed and authenticated, and tell me which services respond.”
  • “List the 20 most recently modified files in my Drive as a table.”
  • “Set up a service account for gws so the nightly job can run without a login.”
  • “Send the weekly update email to the team from the command line.”

Requirements

  • The gws CLI, installed with npm, Cargo or a pre-built binary
  • Python 3 for the helper scripts
  • A Google Cloud OAuth client or a service account key

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Use OAuth with minimal scopes — request only what each workflow needs
  2. Store tokens in the system keyring, never in plain text files
  3. Rotate service account keys every 90 days
  4. Audit third-party OAuth app grants quarterly
  5. Use --dry-run before bulk destructive operations

What it can do on your machine

Read from SKILL.md and the folder at commit e5199b5. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 5 files in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • python3
    • npm
    • cargo

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • github.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • GWS_SERVICE_ACCOUNT_KEY
    • GWS_CLIENT_SECRET

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Google Workspace CLI loads about 2.6k tokens when it runs, and up to ~9.1k if it reads all its reference files. Until then it costs about 86 tokens; SKILL.md has 534 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~86
When it runs · the whole SKILL.md, loaded when a task matches
~2.6k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~9.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteMentions a .env fileSKILL.md:95
    # Generate .env template

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from LeoYeAI/openclaw-master-skills at commit e5199b5, republished under its MIT licence (© LeoYeAI). 534 words, ~2,590 tokens.

Download SKILL.mdSave it as .claude/skills/google-workspace-cli/SKILL.md (or your agent's skills folder). This skill also uses 11 other files; get the full folder from GitHub.
name
google-workspace-cli
description
Google Workspace administration via the gws CLI. Install, authenticate, and automate Gmail, Drive, Sheets, Calendar, Docs, Chat, and Tasks. Run security audits, execute 43 built-in recipes, and use 10 persona bundles. Use for Google Workspace admin, gws CLI setup, Gmail automation, Drive management, or Calendar scheduling.

Google Workspace CLI

Expert guidance and automation for Google Workspace administration using the open-source gws CLI. Covers installation, authentication, 18+ service APIs, 43 built-in recipes, and 10 persona bundles for role-based workflows.

Quick Start

Check Installation
bash
# Verify gws is installed and authenticated
python3 scripts/gws_doctor.py
Send an Email
bash
gws gmail users.messages send me --to "team@company.com" \
  --subject "Weekly Update" --body "Here's this week's summary..."
List Drive Files
bash
gws drive files list --json --limit 20 | python3 scripts/output_analyzer.py --select "name,mimeType,modifiedTime" --format table

Installation

bash
npm install -g @anthropic/gws
gws --version
Cargo (from source)
bash
cargo install gws-cli
gws --version
Pre-built Binaries

Download from github.com/googleworkspace/cli/releases for macOS, Linux, or Windows.

Verify Installation
bash
python3 scripts/gws_doctor.py
# Checks: PATH, version, auth status, service connectivity

Authentication

OAuth Setup (Interactive)
bash
# Step 1: Create Google Cloud project and OAuth credentials
python3 scripts/auth_setup_guide.py --guide oauth

# Step 2: Run auth setup
gws auth setup

# Step 3: Validate
gws auth status --json
Service Account (Headless/CI)
bash
# Generate setup instructions
python3 scripts/auth_setup_guide.py --guide service-account

# Configure with key file
export GWS_SERVICE_ACCOUNT_KEY=/path/to/key.json
export GWS_DELEGATED_USER=admin@company.com
gws auth status
Environment Variables
bash
# Generate .env template
python3 scripts/auth_setup_guide.py --generate-env
VariablePurpose
GWS_CLIENT_IDOAuth client ID
GWS_CLIENT_SECRETOAuth client secret
GWS_TOKEN_PATHCustom token storage path
GWS_SERVICE_ACCOUNT_KEYService account JSON key path
GWS_DELEGATED_USERUser to impersonate (service accounts)
GWS_DEFAULT_FORMATDefault output format (json/ndjson/table)
Validate Authentication
bash
python3 scripts/auth_setup_guide.py --validate --json
# Tests each service endpoint

Workflow 1: Gmail Automation

Goal: Automate email operations — send, search, label, and filter management.

Send and Reply
bash
# Send a new email
gws gmail users.messages send me --to "client@example.com" \
  --subject "Proposal" --body "Please find attached..." \
  --attachment proposal.pdf

# Reply to a thread
gws gmail users.messages reply me --thread-id <THREAD_ID> \
  --body "Thanks for your feedback..."

# Forward a message
gws gmail users.messages forward me --message-id <MSG_ID> \
  --to "manager@company.com"
Search and Filter
bash
# Search emails
gws gmail users.messages list me --query "from:client@example.com after:2025/01/01" --json \
  | python3 scripts/output_analyzer.py --count

# List labels
gws gmail users.labels list me --json

# Create a filter
gws gmail users.settings.filters create me \
  --criteria '{"from":"notifications@service.com"}' \
  --action '{"addLabelIds":["Label_123"],"removeLabelIds":["INBOX"]}'
Bulk Operations
bash
# Archive all read emails older than 30 days
gws gmail users.messages list me --query "is:read older_than:30d" --json \
  | python3 scripts/output_analyzer.py --select "id" --format json \
  | xargs -I {} gws gmail users.messages modify me {} --removeLabelIds INBOX

Workflow 2: Drive & Sheets

Goal: Manage files, create spreadsheets, configure sharing, and export data.

File Operations
bash
# List files
gws drive files list --json --limit 50 \
  | python3 scripts/output_analyzer.py --select "name,mimeType,size" --format table

# Upload a file
gws drive files create --name "Q1 Report" --upload report.pdf \
  --parents <FOLDER_ID>

# Create a Google Sheet
gws sheets spreadsheets create --title "Budget 2026" --json

# Download/export
gws drive files export <FILE_ID> --mime "application/pdf" --output report.pdf
Sharing
bash
# Share with user
gws drive permissions create <FILE_ID> \
  --type user --role writer --emailAddress "colleague@company.com"

# Share with domain (view only)
gws drive permissions create <FILE_ID> \
  --type domain --role reader --domain "company.com"

# List who has access
gws drive permissions list <FILE_ID> --json
Sheets Data
bash
# Read a range
gws sheets spreadsheets.values get <SHEET_ID> --range "Sheet1!A1:D10" --json

# Write data
gws sheets spreadsheets.values update <SHEET_ID> --range "Sheet1!A1" \
  --values '[["Name","Score"],["Alice",95],["Bob",87]]'

# Append rows
gws sheets spreadsheets.values append <SHEET_ID> --range "Sheet1!A1" \
  --values '[["Charlie",92]]'

Workflow 3: Calendar & Meetings

Goal: Schedule events, find available times, and generate standup reports.

Event Management
bash
# Create an event
gws calendar events insert primary \
  --summary "Sprint Planning" \
  --start "2026-03-15T10:00:00" --end "2026-03-15T11:00:00" \
  --attendees "team@company.com" \
  --location "Conference Room A"

# List upcoming events
gws calendar events list primary --timeMin "$(date -u +%Y-%m-%dT%H:%M:%SZ)" \
  --maxResults 10 --json

# Quick event (natural language)
gws helpers quick-event "Lunch with Sarah tomorrow at noon"
Find Available Time
bash
# Check free/busy for multiple people
gws helpers find-time \
  --attendees "alice@co.com,bob@co.com,charlie@co.com" \
  --duration 60 --within "2026-03-15,2026-03-19" --json
Standup Report
bash
# Generate daily standup from calendar + tasks
gws recipes standup-report --json \
  | python3 scripts/output_analyzer.py --format table

# Meeting prep (agenda + attendee info)
gws recipes meeting-prep --event-id <EVENT_ID>

Workflow 4: Security Audit

Goal: Audit Google Workspace security configuration and generate remediation commands.

Run Full Audit
bash
# Full audit across all services
python3 scripts/workspace_audit.py --json

# Audit specific services
python3 scripts/workspace_audit.py --services gmail,drive,calendar

# Demo mode (no gws required)
python3 scripts/workspace_audit.py --demo
Audit Checks
AreaCheckRisk
DriveExternal sharing enabledData exfiltration
GmailAuto-forwarding rulesData exfiltration
GmailDMARC/SPF/DKIM recordsEmail spoofing
CalendarDefault sharing visibilityInformation leak
OAuthThird-party app grantsUnauthorized access
AdminSuper admin countPrivilege escalation
Admin2-Step verification enforcementAccount takeover
Review and Remediate
bash
# Review findings
python3 scripts/workspace_audit.py --json | python3 scripts/output_analyzer.py \
  --filter "status=FAIL" --select "area,check,remediation"

# Execute remediation (example: restrict external sharing)
gws drive about get --json  # Check current settings
# Follow remediation commands from audit output

Python Tools

ScriptPurposeUsage
gws_doctor.pyPre-flight diagnosticspython3 scripts/gws_doctor.py [--json] [--services gmail,drive]
auth_setup_guide.pyGuided auth setuppython3 scripts/auth_setup_guide.py --guide oauth
gws_recipe_runner.pyRecipe catalog & runnerpython3 scripts/gws_recipe_runner.py --list [--persona pm]
workspace_audit.pySecurity/config auditpython3 scripts/workspace_audit.py [--json] [--demo]
output_analyzer.pyJSON/NDJSON analysisgws ... --json | python3 scripts/output_analyzer.py --count

All scripts are stdlib-only, support --json output, and include demo mode with embedded sample data.

Best Practices

Security
  1. Use OAuth with minimal scopes — request only what each workflow needs
  2. Store tokens in the system keyring, never in plain text files
  3. Rotate service account keys every 90 days
  4. Audit third-party OAuth app grants quarterly
  5. Use --dry-run before bulk destructive operations
Show full SKILL.md (195 more words)Show less
Automation
  1. Pipe --json output through output_analyzer.py for filtering and aggregation
  2. Use recipes for multi-step operations instead of chaining raw commands
  3. Select a persona bundle to scope recipes to your role
  4. Use NDJSON format (--format ndjson) for streaming large result sets
  5. Set GWS_DEFAULT_FORMAT=json in your shell profile for scripting
Performance
  1. Use --fields to request only needed fields (reduces payload size)
  2. Use --limit to cap results when browsing
  3. Use --page-all only when you need complete datasets
  4. Batch operations with recipes rather than individual API calls
  5. Cache frequently accessed data (e.g., label IDs, folder IDs) in variables

Limitations

ConstraintImpact
OAuth tokens expire after 1 hourRe-auth needed for long-running scripts
API rate limits (per-user, per-service)Bulk operations may hit 429 errors
Scope requirements vary by serviceMust request correct scopes during auth
Pre-v1.0 CLI statusBreaking changes possible between releases
Google Cloud project requiredFree, but requires setup in Cloud Console
Admin API needs admin privilegesSome audit checks require Workspace Admin role
Required Scopes by Service
bash
# List scopes for specific services
python3 scripts/auth_setup_guide.py --scopes gmail,drive,calendar,sheets
ServiceKey Scopes
Gmailgmail.modify, gmail.send, gmail.labels
Drivedrive.file, drive.metadata.readonly
Sheetsspreadsheets
Calendarcalendar, calendar.events
Adminadmin.directory.user.readonly, admin.directory.group
Taskstasks

© LeoYeAI, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 11 other files (scripts, references, assets) in skills/cs-google-workspace-cli of LeoYeAI/openclaw-master-skills.

  • SKILL.md
  • _meta.json
  • assets/persona-profiles.md
  • assets/workspace-config.json
  • references/gws-command-reference.md
  • references/recipes-cookbook.md
  • references/troubleshooting.md
  • scripts/auth_setup_guide.py
  • scripts/gws_doctor.py
  • scripts/gws_recipe_runner.py
  • scripts/output_analyzer.py
  • scripts/workspace_audit.py

Open the folder on GitHubat commit e5199b5

Compare with similar skills

Google Workspace CLI next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Google Workspace CLI compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Google Workspace CLI this skillLeoYeAI/openclaw-master-skills2.2k—~2.6kAutomated safety check: NotesMIT
Prismer Google WorkspacePrismer-AI/PrismerCloud1.6k3 repos~4.2kAutomated safety check: PassMIT
Google Workspace CLIlaude-institute/headlong1.2k—~1.2kAutomated safety check: PassApache-2.0
Google Workspace CLIalirezarezvani/claude-skills28k—~3kAutomated safety check: NotesMIT
Google Workspaceericrisco/rsc-harness156—~3.2kAutomated safety check: PassMIT
Google Workspaceyc-software/qm15k—~1.8kAutomated safety check: PassMIT

Similar skills

  • Prismer Google Workspace

    Prismer-AI/PrismerCloud

    Gives an agent account-scoped access to Gmail, Calendar, Drive, Contacts, Docs and Sheets through the gws CLI or a bundled Python client.

    1.6k GitHub starsUsed in 3 repos~4.2k tokens
    Productivity & AutomationAuto-check passed

  • Google Workspace CLI

    laude-institute/headlong

    Drives Google Drive, Gmail, Calendar, Sheets, Docs and Chat from the shell with the gws CLI, including its sign-in, flags, helper commands and safety rules.

    1.2k GitHub stars~1.2k tokensUpdated today
    Productivity & AutomationAuto-check passed

  • Google Workspace CLI

    alirezarezvani/claude-skills

    Google Workspace administration via the gws CLI (github.com/googleworkspace/cli).

    28k GitHub stars~3k tokensUpdated 1 mo ago
    Documents & OfficeAuto-check: notes

  • Google Workspace

    ericrisco/rsc-harness

    A skill your agent uses when server-side code reads or writes Gmail, Drive, Calendar, or Sheets with a GCP service account and no human in the OAuth loop: picking the auth mode (app-owned vs…

    156 GitHub stars~3.2k tokensUpdated today
    Backend & APIsAuto-check passed

  • Google Workspace

    yc-software/qm

    Read and act on the user's Gmail, Google Calendar, and Google Tasks through per-user OAuth.

    15k GitHub stars~1.8k tokensUpdated today
    Productivity & AutomationAuto-check passed

  • Gog

    trpc-group/trpc-agent-go

    Google Workspace CLI for Gmail, Calendar, Drive, Contacts, Sheets, and Docs.

    1.8k GitHub starsUsed in 14 repos~1.1k tokens
    Productivity & AutomationAuto-check passed

More from LeoYeAI/openclaw-master-skills

All 1,215 skills in this repo

  • DevOps Pipeline Management

    LeoYeAI/openclaw-master-skills

    Manages pipelines on a DevOps quality and efficiency platform through its OpenAPI: list workspaces and templates, create, update, run and cancel pipelines, and read run records.

    2.2k GitHub stars~4.2k tokensUpdated 2 mo ago
    Auto-check: notes

  • Feishu Document Collaboration

    LeoYeAI/openclaw-master-skills

    Patches OpenClaw's Feishu extension so an edited document triggers an isolated agent session that reads the doc and replies inline, turning it into a live chat space.

    2.2k GitHub stars~2k tokensUpdated 2 mo ago
    Auto-check passed

  • Files Memory System

    LeoYeAI/openclaw-master-skills

    Multi-context memory management system for OpenClaw agents with group-isolated storage, global shared memory, workspace organization, and group-specific skills isolation.

    2.2k GitHub stars~3.8k tokensUpdated 2 mo ago
    Auto-check passed

  • GEO-Claw AI Visibility Agent

    LeoYeAI/openclaw-master-skills

    Runs a brand's AI-search visibility work end to end: diagnosing how AI platforms represent it, repositioning it, producing AI-optimized content and monitoring ongoing mentions.

    2.2k GitHub stars~4.7k tokensUpdated 2 mo ago
    Auto-check passed

  • HealthFit Health Advisors

    LeoYeAI/openclaw-master-skills

    Runs four advisor roles, a fitness coach, nutritionist, data analyst and TCM practitioner, to build a health profile and track workouts, diet and wellness over time.

    2.2k GitHub stars~4.4k tokensUpdated 2 mo ago
    Auto-check passed

  • Humanizer

    LeoYeAI/openclaw-master-skills

    Humanize AI-generated text by detecting and removing patterns typical of LLM output.

    2.2k GitHub stars~2k tokensUpdated 2 mo ago
    Auto-check passed

Works with

Categories

Questions about Google Workspace CLI

What does Google Workspace CLI do?

Installs and authenticates the gws CLI, then automates Gmail, Drive, Sheets, Calendar, Docs, Chat and Tasks with ready-made recipes, persona bundles and security audits. This skill guides the agent through administering Google Workspace with the open-source gws command-line tool. It covers installing gws through npm, Cargo or a pre-built binary, and signing in with an interactive OAuth flow or with a service account for headless and CI use.

When should I use Google Workspace CLI?

Google Workspace CLI fits situations like: setting up and authenticating the gws CLI for a Google Workspace account; automating Gmail sending, search, labels or filters from the command line; listing or managing Drive files and Calendar events in bulk; running a security audit of a Google Workspace account.

How do I install Google Workspace CLI in Claude Code?

Run `npx skills add LeoYeAI/openclaw-master-skills --skill google-workspace-cli -a claude-code`. Or copy the skill folder (skills/cs-google-workspace-cli in LeoYeAI/openclaw-master-skills) into .claude/skills/google-workspace-cli in your project. Claude Code loads it when a task matches its description.

How do I install Google Workspace CLI in Codex?

Run `npx skills add LeoYeAI/openclaw-master-skills --skill google-workspace-cli -a codex`. Or copy the skill folder (skills/cs-google-workspace-cli in LeoYeAI/openclaw-master-skills) into .agents/skills/google-workspace-cli in your project. Codex loads it when a task matches its description.

Can I use Google Workspace CLI in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add LeoYeAI/openclaw-master-skills --skill google-workspace-cli -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/google-workspace-cli, .gemini/skills/google-workspace-cli, .github/skills/google-workspace-cli and .opencode/skills/google-workspace-cli in your project.

What does Google Workspace CLI need to run?

Going by SKILL.md and its folder, Google Workspace CLI needs Python for the scripts in its folder, the command-line tools its instructions call (python3, npm and cargo) and credentials named GWS_SERVICE_ACCOUNT_KEY and GWS_CLIENT_SECRET. Our summary lists: The gws CLI, installed with npm, Cargo or a pre-built binary; Python 3 for the helper scripts; A Google Cloud OAuth client or a service account key.

Does Google Workspace CLI access the network?

SKILL.md names 1 domain. As links in the text: github.com. This is read from the text; nothing was executed.

Is Google Workspace CLI safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Google Workspace CLI use?

Google Workspace CLI is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Google Workspace CLI use?

About 2.6k tokens (SKILL.md is roughly 10k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 6.5k tokens, read only when the agent opens those files.

What are the alternatives to Google Workspace CLI?

Skills that share tags, products or a category with Google Workspace CLI: Prismer Google Workspace (Prismer-AI/PrismerCloud, 1.6k stars), Google Workspace CLI (laude-institute/headlong, 1.2k stars), Google Workspace CLI (alirezarezvani/claude-skills, 28k stars) and Google Workspace (ericrisco/rsc-harness, 156 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Google Workspace CLI?

LeoYeAI (a GitHub user) maintains it in LeoYeAI/openclaw-master-skills, which has 2,158 GitHub stars. The repository holds 1,215 skills in this directory. The repository was last updated on July 20, 2026.

Source: LeoYeAI/openclaw-master-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.