Verified:GitHub

gws-common

Enforce gws CLI conventions for authentication, JSON output, and error handling.

18|7|Updated Mar 11, 2026

Search Tags:#authentication #error handling #cli #conventions #google workspace #gws

One-click install

npx skills add https://github.com/thecloudtips/founder-os --skill gws-common

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: gws-common
Source: https://github.com/thecloudtips/founder-os/tree/main/plugin/skills/infrastructure/gws-common
Command: npx skills add https://github.com/thecloudtips/founder-os --skill gws-common

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill establishes standardized conventions for interacting with Google Workspace services (Gmail, Calendar, Drive) via the gws CLI, ensuring consistency and graceful degradation across all Founder OS plugins.

Core Features & Use Cases

Standardized Authentication: Ensures gws CLI is authenticated without per-plugin setup.
Consistent Output Formatting: Mandates JSON output for all gws commands for reliable parsing.
Robust Error Handling: Defines clear actions for various exit codes, including retries and graceful degradation.
Rate Limit Management: Provides guidelines for handling Google API rate limits.
Use Case: When any Founder OS plugin needs to access user emails, it will first check for gws availability and use the defined JSON output and error handling to process the data, degrading gracefully if Google services are unavailable.

Quick Start

Ensure the gws CLI is installed and authenticated before running any Google Workspace commands.

Frequently Asked Questions about gws-common

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

FAQPage Schema

How do I standardize Google Workspace CLI authentication across multiple plugins?▼

Google Workspace CLI JSON output formatting enforces JSON output for all gws commands, ensuring reliable parsing of Gmail, Calendar, and Drive data across all plugins.

How do I handle Google API rate limits and error codes when using the gws CLI?▼

Use gws CLI conventions for Google Workspace to enforce standardized authentication, JSON output formatting, robust error handling, and rate limit awareness across all plugins.

Does the gws CLI require separate authentication for each Google Workspace plugin?▼

Yes, the gws CLI works with Gmail, Calendar, and Drive, applying global conventions for JSON output formatting and error handling to all Google Workspace data interactions.

What are the limitations when Google Workspace services are unavailable via the gws CLI?▼

Use gws CLI conventions for Google Workspace to enforce standardized authentication, JSON output formatting, robust error handling, and rate limit awareness across all plugins.