Google Workspace

This is the routing layer you want before you touch any Google Workspace API. It forces you to answer the hard question first: Apps Script, direct REST, or Admin SDK? The skill walks through five classification questions (surface, operation, actor, execution home, trigger), maps them to auth models, and gives you workflow packets for common cross-service jobs like form intake or approval flows. The best part is the route-out logic: it tells you when you're over-engineering a spreadsheet problem or when you actually need domain-wide delegation. If you've ever started writing Sheets code only to realize halfway through that you picked the wrong surface, this will save you that rewrite.

skills.sh installs: 177
GitHub stars: 22
last updated: Jun 3, 2026

View on GitHub

Install

$ npx -y skills add akillness/oh-my-skills --skill google-workspace --agent claude-code

Installs into .claude/skills of the current project.

Files

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