Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
akillness avatar

Google Workspace

  • 285 installs
  • 40 repo stars
  • Updated August 4, 2026
  • akillness/oh-my-skills

google-workspace is an agent skill that routes Google Workspace automation across Docs, Sheets, Gmail, Calendar, Drive, Forms, Chat, and Admin SDK by selecting Apps Script, REST APIs, or admin-only flows for developers i

About

google-workspace is an Apache-2.0 skill (version 1.1.0) from akillness/oh-my-skills that plans Google Workspace automations before writing code. It classifies requests across nine product surfaces—Docs, Sheets, Slides, Drive, Gmail, Calendar, Forms, Chat, and Admin SDK—and chooses Apps Script for bound triggers, direct REST plus google-api-python-client for backend services, or Admin SDK for directory tasks. Auth guidance covers OAuth user flows, service accounts, and domain-wide delegation with narrow scopes. Workflow packets include Form→Sheet→Gmail intake, Sheet approval queues, and reporting flows with idempotency and quota checks. Three reference files detail auth routing, service selection, and cross-service patterns. Invoke when automating spreadsheets, shared drives, inbox workflows, or domain admin changes.

  • Unified Google Workspace actions for agent workflows
  • Supports document, spreadsheet, and email automation
  • Reduces custom OAuth and API boilerplate per task
  • Fits SaaS teams embedding productivity assistants

Google Workspace by the numbers

  • 285 all-time installs (skills.sh)
  • Ranked #497 of 2,715 Automation & Workflows skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/akillness/oh-my-skills --skill google-workspace

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs285
repo stars40
Last updatedAugust 4, 2026
Repositoryakillness/oh-my-skills

How do you automate Google Workspace APIs?

Connect agents to Google Workspace so they can read Gmail, edit Docs, update Sheets, and manage Drive files inside automated business workflows.

Who is it for?

Integration engineers automating multi-app Google Workspace flows who need auth, scope, and Apps Script versus REST routing before implementation.

Skip if: Teams wanting only generic Zapier tutorials without Google API scope planning or Workspace-specific quota analysis.

When should I use this skill?

User mentions Google Sheets automation, Gmail send, Calendar events, Drive sharing, Forms pipelines, Apps Script, or Admin SDK tasks.

What you get

Execution packet with chosen API surface, auth model, scopes, object IDs, workflow sequence, and verification steps for Workspace automation.

  • integration execution packet
  • scope and auth plan
  • Workspace automation scripts

By the numbers

  • Skill metadata version 1.1.0 under Apache-2.0 license
  • Routes automation across 9 Google Workspace product surfaces
  • Includes 3 reference guides for auth, services, and workflow quotas

Files

SKILL.mdMarkdownGitHub ↗

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
  • you need stronger control over deployment, testing, retries, or non-JS stacks
  • the task spans Workspace plus external systems and should not depend on a bound script runtime
  • Apps Script quotas or runtime limits are likely to be the bottleneck
Use Admin SDK / admin APIs when
  • the job is about users, groups, org units, roles, or domain administration
  • domain-wide delegated access is part of the task
  • the request is clearly beyond ordinary content operations like Docs/Sheets editing
Use an external automation layer only as a route-out
  • If the user really needs a no-code / cross-app orchestrator, mention tools like Zapier / Make / n8n as substitutes.
  • Do not turn this skill into a generic no-code platform tutorial.

Step 3: Pick the auth model

Auth modelUse whenTypical surfacesNotes
OAuth user flowActing on a real user’s mailbox, calendar, Drive, docs, or personal contentGmail, Calendar, Drive, Docs, Sheets, Slides, Forms, ChatBest default for user-owned data
Service accountBackend automation owns the data or operates on shared resourcesDrive, backend-generated docs/sheets, service workflowsMay need shared-drive/file access design
Service account + domain-wide delegationAdmin or org-wide actions must impersonate users safelyAdmin SDK, org-wide Gmail/Calendar/Drive workflowsHigher security burden; keep scope narrow
Apps Script-bound authThe workflow is intentionally inside Workspace and tied to the script owner / install modelSheets, Docs, Forms, Gmail, Calendar, DriveFast to start, but runtime/quotas still matter

Rules:

  • Choose the narrowest scopes that satisfy the task.
  • Keep credentials and tokens out of the repo.
  • If the task touches a user’s mailbox/calendar/files, say whose identity is acting.
  • If admin powers are required, separate that packet from ordinary content-editing logic.

Step 4: Route to the right Workspace product

ProductGood forCommon operationsRoute out when
Docsformatted text documentscreate docs, replace placeholders, insert text/tables/images, exportthe deliverable is really a slide deck or spreadsheet
Sheetstabular workflows and lightweight ops databasesappend/update rows, formatting, formulas, filters, approvals, dashboardsthe user needs durable database design or BI modeling
Slidesgenerated presentations and updateable deckscreate slides, replace placeholders, thumbnails, batch updatesthe real job is deck strategy/content design rather than API execution
Drivestorage, sharing, folder hierarchy, export/importupload files, create folders, search files, permissions, shared drivesthe main problem is information architecture rather than Drive API calls
Gmailmailbox automation and outbound messagesdrafts, send, labels, search, thread actionsthe main job is email writing strategy rather than mailbox ops
Calendarscheduling and event automationcreate events, invite attendees, sync timing, Meet linksthe core issue is meeting policy or roadmap planning
Formsintake, surveys, quizzes, response pipelinescreate/update forms, response collection, Form → Sheet workflowsthe job is survey design methodology rather than implementation
Chatworkspace messaging automationspost messages, bot flows, notificationsthe user needs broader chatops platform design
Admin SDKdirectory and domain administrationusers, groups, org units, licenses, settingsordinary content workflows are being over-administered

Step 5: Use workflow packets for common cross-service jobs

Form intake packet
  • Forms captures submissions
  • Sheets stores / reviews responses
  • Gmail or Chat sends follow-up notifications
  • Calendar schedules interviews, meetings, or reminders when needed
Approval / operations packet
  • Sheet stores queue/state
  • Apps Script or backend worker evaluates rows / statuses
  • Gmail or Chat sends approval prompts / updates
  • Drive stores generated artifacts or attachments
Reporting packet
  • Sheets holds metrics or extracts
  • Docs / Slides publish the narrative output
  • Drive manages shared access and exports
  • Calendar / Gmail handles scheduled distribution

For multi-step flows, define:

  • system of record
  • trigger source
  • actor identity
  • idempotency / duplicate-submission rule
  • failure notification path

Step 6: Check quota and runtime risk

Before finalizing the plan, ask whether the workflow is:

  • high-volume or bulk-edit heavy
  • schedule-driven with frequent triggers
  • likely to hit Apps Script execution/runtime limits
  • dependent on large Drive traversals, Gmail sends, or spreadsheet write bursts

If yes:

  • prefer batch operations where supported
  • avoid row-by-row chatty loops when one batch call exists
  • consider moving from Apps Script to a backend worker if runtime ceilings become the real constraint

Step 7: Produce a concrete execution packet

Return a compact plan with:

  • chosen Workspace surface
  • chosen auth model
  • required scopes / admin boundaries
  • primary object identifiers needed (docId, spreadsheetId, folderId, user email, calendarId, formId)
  • implementation sequence
  • verification step
  • route-outs / risks

Examples

Example 1: Form → Sheet → email workflow

Prompt: “Create an employee feedback form, collect responses in Sheets, and send a confirmation email.”

Use this skill to:

  • classify it as a multi-service workflow
  • choose Apps Script or a lightweight backend depending on where the automation should live
  • identify Forms + Sheets + Gmail as the service bundle
  • specify auth/scopes and trigger behavior before implementation

Example 2: Shared Drive onboarding packet

Prompt: “Create a shared Drive folder structure for a new client, share it with three users, and generate a kickoff doc.”

Use this skill to:

  • route Drive as the primary surface and Docs as the secondary artifact layer
  • choose OAuth or service-account access based on ownership model
  • list folder IDs, user emails, and sharing rules before coding

Example 3: Workspace admin request

Prompt: “Suspend a departing user, move them to a different org unit, and audit their group membership.”

Use this skill to:

  • route immediately to Admin SDK
  • require admin/delegated identity clarification in the execution packet
  • keep admin actions separate from ordinary Docs/Drive editing logic

Example 4: Sheet-heavy approvals automation

Prompt: “Turn this spreadsheet into an approvals queue with reminder emails and status updates.”

Use this skill to:

  • decide whether bound Apps Script is enough
  • define status columns, reminder cadence, and Gmail integration
  • check quota/runtime risk before promising a trigger-heavy solution

Best practices

1. Start with surface choice, not code snippets. 2. Separate content operations from admin operations. 3. Use Apps Script for Workspace-native ergonomics; use direct APIs when backend control or scale matters more. 4. Keep scopes narrow and state exactly whose identity is acting. 5. For multi-app workflows, define the source of truth and trigger source first. 6. Prefer batch updates over chatty per-row / per-cell loops when the API supports batching. 7. If the problem is actually writing emails, documents, surveys, dashboards, or presentations, route to the corresponding content skill after the Workspace execution packet is clear.

References

  • references/auth-and-scope-routing.md — OAuth vs service account vs domain-wide delegation routing
  • references/service-selection-matrix.md — product-by-product routing across Docs / Sheets / Drive / Gmail / Calendar / Forms / Admin SDK
  • references/workflow-patterns-and-quotas.md — common cross-service packets plus quota/runtime cautions
  • Google Workspace developer docs: https://developers.google.com/workspace
  • Auth overview: https://developers.google.com/workspace/guides/auth-overview
  • Apps Script samples: https://developers.google.com/apps-script/samples
  • Apps Script quotas: https://developers.google.com/apps-script/guides/services/quotas
  • Forms REST vs Apps Script comparison: https://developers.google.com/workspace/forms/api/guides/compare-rest-apps-script

Related skills

How it compares

Use google-workspace for API routing and auth planning; use document-format skills when the deliverable is file content design rather than API integration.

FAQ

When does google-workspace recommend Apps Script?

google-workspace recommends Apps Script when workflows center on Sheets, Docs, or Forms with triggers, custom menus, or bound scripts inside Workspace. Backend services spanning external systems should use direct REST APIs with google-api-python-client instead.

Which Google products does google-workspace cover?

google-workspace routes automation across Docs, Sheets, Slides, Drive, Gmail, Calendar, Forms, Chat, and Admin SDK. Version 1.1.0 includes three reference files for auth models, per-product routing, and quota-aware workflow patterns.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.