google-workspace

Wrap the gws CLI to integrate Google Workspace services with OAuth token refresh.

Updated Apr 16, 2026

Search Tags:#automation #oauth #gmail #calendar #drive #google-workspace #gws

Ready to run

npx skills add https://github.com/jacardl/New-Radar --skill google-workspace-jacardl

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: google-workspace
Source: https://github.com/jacardl/New-Radar/tree/main/backend/frameworks/hermes-agent/skills/productivity/google-workspace
Command: npx skills add https://github.com/jacardl/New-Radar --skill google-workspace-jacardl

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires google-api-python-client, google-auth-oauthlib, google-auth-httplib2, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Gmail, Calendar, Drive, Contacts, Sheets, and Docs — powered by gws (Google's official Rust CLI). The skill provides a backward-compatible Python wrapper that handles OAuth token refresh and delegates to gws.

Core Features & Use Cases

Backward-compatible Python wrapper around gws that preserves the same CLI interface.
Automatic OAuth token refresh via gws_bridge.py, enabling seamless, headless authentication.
Unified interface for Gmail, Calendar, Drive, Sheets, Docs, and Contacts with setup guidance.

Quick Start

Authenticate once using the setup flow and then issue Gmail, Calendar, Drive, Sheets, Docs, and Contacts commands through the wrapper.

Frequently Asked Questions about google-workspace

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate Gmail, Calendar, and Drive operations through a single interface?▼

This Skill provides a backward-compatible Python wrapper around the gws CLI to automate Gmail, Calendar, Drive, Sheets, Docs, and Contacts operations through a single unified interface.

What is the best way to handle OAuth token refresh for Google Workspace automation?▼

The built-in gws_bridge.py automatically manages OAuth token refresh by reading google_token.json and google_client_secret.json, enabling seamless headless authentication for Google Workspace CLI operations.

Can I use the gws CLI with Python for headless Google Workspace authentication?▼

Yes, the Python wrapper bridges to the gws CLI for headless authentication by automatically injecting the access token from google_token.json and google_client_secret.json files.

Does this Google Workspace wrapper require setting up credentials for each service separately?▼

No, you authenticate once using the setup flow, then issue Gmail, Calendar, Drive, Sheets, Docs, and Contacts commands through the unified wrapper without separate credential setups.

Why does my Google Workspace automation script need a backward-compatible API wrapper?▼

A backward-compatible API wrapper preserves the same CLI interface while delegating commands to gws, ensuring existing workflows remain functional without requiring code changes during updates.