gog

Interact with Google Workspace APIs via a sandboxed command-line interface.

Updated Jun 1, 2026
One-click install
npx skills add https://github.com/PicoMLX/SwiftGog --skill gog-picomlx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gog
Source: https://github.com/PicoMLX/SwiftGog/tree/main/.agents/skills/gog
Command: npx skills add https://github.com/PicoMLX/SwiftGog --skill gog-picomlx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the challenge of securely interacting with Google Workspace services from within a sandboxed shell environment, enabling automated data management without exposing credentials or bypassing security policies.

Core Features & Use Cases

  • Secure Workspace Access: Perform read and write operations across Drive, Gmail, Calendar, Tasks, Sheets, and more using a host-injected token.
  • JSON-First Integration: Output structured data directly to stdout, making it ideal for piping into tools like jq for complex shell automation.
  • Host-Gated Safety: Enforce strict write-tier policies and network allow-listing to ensure that automated scripts cannot perform unauthorized mutations or data exfiltration.

Quick Start

Use the gog skill to list the names of the twenty most recent files in your Google Drive as a JSON array.

Frequently Asked Questions about gog

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

FAQPage Schema
How do I automate Google Workspace tasks from a sandboxed shell environment?

You can automate Google Workspace tasks using a sandboxed command-line interface that interacts with Drive, Gmail, and Calendar APIs. It enforces strict write-tier gating and network allow-listing to ensure scripts cannot perform unauthorized mutations or data exfiltration.

Can I get JSON output from Google Drive and Gmail CLI commands for shell automation?

Yes, the Google Workspace CLI outputs structured JSON data directly to stdout. This JSON-first integration makes it ideal for piping command results into tools like jq for complex shell automation workflows.

Does the Google Workspace CLI require manual authentication for automated scripts?

No, manual authentication is not required. The Google Workspace CLI operates securely within restricted shell environments using host-managed authentication, relying on a host-injected token to access APIs without exposing credentials.

What Google Workspace APIs can I interact with using this CLI tool?

You can interact with multiple Google Workspace APIs including Drive, Gmail, Calendar, Tasks, and Sheets. The CLI supports both read and write operations across these services within your automated data retrieval and mutation tasks.

What are the security limitations of automating Google Workspace API mutations in a sandbox?

Security limitations include strict write-tier policies and network allow-listing that restrict automated scripts. These constraints ensure that sandboxed environments cannot perform unauthorized data mutations or bypass established security policies.