google_workspace

Manage Google OAuth tokens and pass through gws CLI commands.

10|Updated Feb 17, 2026
One-click install
npx skills add https://github.com/istota-project/istota --skill google-workspace-istota-project
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: google_workspace
Source: https://github.com/istota-project/istota/tree/main/src/istota/skills/google_workspace
Command: npx skills add https://github.com/istota-project/istota --skill google-workspace-istota-project

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides secure, token-managed access to Google Workspace tools via the gws CLI, enabling automated workflows without embedding credentials in commands.

Core Features & Use Cases

  • Secure authentication through the Istota skill proxy; credentials are never exposed in user commands.
  • Automatic token refresh and configuration of the gws CLI environment (GOOGLE_WORKSPACE_CLI_TOKEN and GOOGLE_WORKSPACE_CLI_CONFIG_DIR) to sustain long-running tasks.
  • Transparent passthrough of Google Workspace commands (Drive, Docs, Sheets, Calendar, Gmail, Chat) for automated workflows and integrations.

Quick Start

List all files in Google Drive using istota-skill google_workspace drive files list.

Frequently Asked Questions about google_workspace

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

FAQPage Schema
How do I automate Google Workspace tasks without exposing credentials in CLI commands?

You can secure Google Workspace automation by using a CLI proxy that injects and manages OAuth tokens directly, ensuring credentials are never embedded in user commands. This enables safe, transparent passthrough for Drive, Docs, Sheets, Calendar, Gmail, and Chat workflows.

How does automatic token refresh work for long-running Google Workspace workflows?

Automatic token refresh sustains long-running Google Workspace workflows by continuously updating the OAuth token environment configuration. This prevents authentication timeouts during extended automated tasks without requiring manual re-authentication.

Can I use the gws CLI tool with Google Drive, Sheets, and Gmail automation?

Yes, the gws CLI tool supports transparent command passthrough for Google Drive, Sheets, Docs, Calendar, Gmail, and Chat automation. It configures the necessary token and directory environment variables to enable these integrations securely.

What is the best way to manage Google OAuth tokens for environment-isolated automation?

The best way to manage Google OAuth tokens for isolated automation is through a secure proxy configuration that handles credential injection and environment variable setup automatically. This satisfies strict requirements for token management and safe environment isolation.

Why does my Google Workspace CLI integration require a proxy configuration?

A proxy configuration is required for Google Workspace CLI integration to ensure secure authentication and automatic token refresh. It safely handles credential injection so long-running automated workflows can access Google services without exposing sensitive data.