google-workspace

# Google Workspace Use this skill for Google Workspace workflows that go beyond HybridClaw's built-in email and Discord channels. For API-backed Google Workspace access, prefer the bundled `gws` or `gog` skill when available. ## Scope - Gmail searches and draft/send workflows - Calendar event review and creation - Drive file lookup - Docs and Sheets editing or export workflows - setup guidance for Google Cloud OAuth credentials or existing Google tooling ## Default Strategy 1. For API-backed Gmail, Calendar, Drive, Contacts, Sheets, or Docs tasks, use the bundled `gws` skill first when it is installed. Use `gog` when it is a better fit for the command surface or `gws` is unavailable. 2. Start by running exactly `gws auth status` or `gog`'s equivalent lightweight status/help command. Do not run `gws auth status --json`; auth status already prints JSON and does not accept `--json`. For `gws`, treat `credential_source: "token_env_var"` or `token_env_var: true` as authenticated even when `auth_method` is `"none"`, because HybridClaw injects `GOOGLE_WORKSPACE_CLI_TOKEN`. If the CLI reports no usable auth, tell the user to run `hybridclaw auth login google`; do not ask for `hybridclaw browser login`. 3. For email-only tasks where `gws` and `gog` are unavailable, prefer the optional `himalaya` community skill if it is installed, or the existing email channel when that is simpler. 4. Use browser automation only when the user explicitly asks for browser-based work or the task ne...