Google Workspace Ecosystem
Google Workspace is the personal/work productivity route when tasks involve Gmail, Drive, Calendar, Sheets, Docs, Slides, Tasks, or Workspace API-backed local sync. Source: Ecosystem Capability Coverage, 2026-06-27; Skill Resolver, 2026-06-27
When To Use This
Use Google Workspace for user productivity data and actions. Do not confuse it with Google Cloud or Firebase: Workspace is Gmail/Drive/Calendar/Docs-style user data, while Firebase and GCP are application/cloud infrastructure. Source: Skill Resolver, 2026-06-27
Decision Matrix
| Need | Route | Verification |
|---|---|---|
| Drive/Gmail/Calendar/Sheets/Docs | gws-* skills |
Read/list result or write ID |
| Lower-level API method | Google Workspace CLI | gws schema or dry-run/result |
| Local sync to wiki | sync scripts | Updated raw/wiki state |
| Send/write/upload/create | Skill after approval | Link/ID plus account |
Core Model
Google Workspace is high-trust personal data. Reads should be scoped. Writes require explicit confirmation. Durable discoveries should be compiled into the wiki rather than left as chat memory. Source: Memory Routing Protocol, 2026-06-27; Skill Resolver, 2026-06-27
Routing Summary
Preferred order: gws-* skills for task procedures, Google Workspace CLI for raw API reach, local sync scripts for ingestion, and wiki pages for durable results. Source: Skill Resolver, 2026-06-27
Failure Modes
- Sending email or writing docs without approval.
- Losing account/file/calendar/thread identity.
- Treating Workspace APIs as Firebase/GCP.
- Leaving extracted facts uncompiled.
Verification Path
Read/list first and return account, resource ID, URL, or timestamp. Use dry-run where available before writes, and ask before send/write/upload/create operations. Source: Google Workspace CLI, 2026-06-25; Skill Resolver, 2026-06-27
Timeline
- 2026-06-27 | Canonical ecosystem page created to sit above the
gws-*skill family and Google Workspace CLI tool page. Source: User request, 2026-06-27; Ecosystem Capability Coverage