google-workspace

name	google-workspace
description	Plan and execute Google Workspace operations across Docs, Sheets, Slides, Drive, Gmail, Calendar, Forms, Chat, and Admin SDK by choosing the right surface first: Apps Script, direct REST API, or admin-only APIs. Use when the user needs to automate a Workspace workflow, edit or create Workspace files, send Gmail, schedule calendar events, process Forms/Sheets pipelines, manage Drive sharing, or handle Workspace admin tasks; even if they only mention a spreadsheet, document, shared drive, inbox workflow, approval flow, or domain user change. Triggers on: Google Doc, Google Sheet, spreadsheet, Slides, Drive folder, Gmail, calendar event, Forms, Apps Script, Admin SDK, shared drive, Google Chat, workspace automation, domain user, send email, approval flow.
allowed-tools	Bash Read Write Edit Glob Grep
license	Apache-2.0
compatibility	Requires Python 3.8+ plus google-api-python-client / google-auth libraries for direct API use. Apps Script routes are valid when the workflow should live inside Workspace.
metadata	{"tags":"google-workspace, google-docs, google-sheets, google-slides, google-drive, gmail, google-calendar, google-chat, google-forms, admin-sdk, apps-script, automation","version":"1.1.0","author":"Agent Skills Team","platforms":"Claude, Gemini, Codex, OpenCode"}

Google Workspace

Use this skill to route Google Workspace work before writing code or pasting API snippets. The key decision is usually which Workspace surface should own the job:

• Apps Script for Workspace-native automation close to Sheets / Docs / Forms / triggers / menus
• Direct REST API + client libraries for backend services, multi-system integrations, stronger deployment control, or language flexibility
• Admin SDK / admin-only APIs for users, groups, org units, directory data, or domain-wide governance tasks

When to use this skill

• Create or update Docs, Sheets, Slides, Drive files/folders, Gmail messages, Calendar events, Forms, or Chat messages
• Design a Workspace automation flow such as Form → Sheet → Gmail / Calendar / Drive
• Decide between Apps Script and direct REST APIs
• Choose the right auth model: OAuth user flow, service account, or domain-wide delegation
• Review scopes, sharing model, quota/execution risk, or safety boundaries before implementation
• Handle Workspace admin tasks that ordinary Docs/Sheets/Gmail code should not absorb

Instructions

Step 1: Classify the request

Capture five things before touching any API:

1. Primary product surface — Docs, Sheets, Slides, Drive, Gmail, Calendar, Forms, Chat, or Admin SDK
2. Operation — create, read, update, search, share, send, schedule, export, batch update, administer
3. Actor / identity — end user, service account, delegated admin, or Apps Script owner
4. Execution home — inside Workspace UI/runtime, backend service, cron/batch worker, or mixed workflow
5. Trigger / cadence — manual, form submit, scheduled, web request, bulk migration, admin event

If the user describes multiple Workspace apps, treat it as a workflow problem first, not a single-API problem.

Step 2: Choose the execution surface

Use Apps Script when

• the workflow is centered around Sheets / Docs / Forms / Gmail and should live inside Workspace
• you need triggers, custom menus, sidebars, or other Workspace-native scripting behavior
• a bound script is simpler than provisioning a separate backend
• JavaScript-in-Workspace ergonomics matter more than backend deployment control

Use direct REST APIs when

• the workflow lives in a backend, integration service, CLI, or batch job