gws-sharedgws CLI: Shared patterns for authentication, global flags, and output formatting.
Install via ClawdBot CLI:
clawdbot install googleworkspace-bot/gws-sharedGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Calls external URL not in known-safe list
https://github.com/googleworkspace/cli`Audited Apr 16, 2026 · audit v1.0
Generated Mar 20, 2026
An IT administrator uses gws-shared to automate user provisioning and deprovisioning across Google Workspace services like Drive and Gmail. They script bulk operations with --json flags for request bodies and --dry-run for validation, ensuring compliance and reducing manual errors in onboarding/offboarding processes.
A data analyst extracts and formats data from Google Sheets for business reports using gws-shared. They utilize --params for querying specific ranges and --format csv or json for output, integrating the CLI into automated pipelines to generate daily insights without manual spreadsheet access.
A security auditor scans Google Drive for sensitive information by running gws-shared commands with --sanitize to screen PII. They use --page-all to paginate through large file lists and --output to save logs, helping organizations maintain data privacy and regulatory compliance efficiently.
A marketing team manages campaign assets stored in Google Drive, using gws-shared to upload files with --upload and organize metadata via --json. They automate updates across multiple resources, leveraging --format table for quick reviews and ensuring consistent branding across digital channels.
A company builds a SaaS platform that integrates gws-shared to offer automated Google Workspace management tools to clients. They charge subscription fees based on usage tiers, providing features like user analytics and compliance reporting, with revenue generated from monthly or annual licenses.
A consulting firm uses gws-shared to deliver custom automation solutions for businesses migrating to or optimizing Google Workspace. They offer one-time project fees and ongoing support contracts, generating revenue by reducing clients' operational costs through tailored CLI scripts and training.
A developer community monetizes gws-shared by providing premium support, custom extensions, and enterprise features around the open-source CLI. Revenue comes from paid support plans, sponsored features, and donations, leveraging the project's GitHub repository for community engagement and issue tracking.
💬 Integration Tip
Integrate gws-shared into existing DevOps pipelines by using environment variables for authentication and scripting common operations with --dry-run first to validate commands before full execution.
Scored Apr 19, 2026
Self-hosted auth for TypeScript/Cloudflare Workers with social auth, 2FA, passkeys, organizations, RBAC, and 15+ plugins. Requires Drizzle ORM or Kysely for D1 (no direct adapter). Self-hosted alternative to Clerk/Auth.js. Use when: self-hosting auth on D1, building OAuth provider, multi-tenant SaaS, or troubleshooting D1 adapter errors, session caching, rate limits, Expo crashes, additionalFields bugs.
Clerk integration. Manage Users, Organizations. Use when the user wants to interact with Clerk data.
Clerk auth with API Keys beta (Dec 2025), Next.js 16 proxy.ts (March 2025 CVE context), API version 2025-11-10 breaking changes, clerkMiddleware() options, webhooks, production considerations (GCP outages), and component reference. Prevents 15 documented errors. Use when: API keys for users/orgs, Next.js 16 middleware filename, troubleshooting JWKS/CSRF/JWT/token-type-mismatch errors, webhook verification, user type inconsistencies, or testing with 424242 OTP.
Sentry API integration with managed authentication. Monitor errors, issues, and application performance. Use this skill when users want to list issues, retrieve events, manage projects, teams, or releases in Sentry. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a Sentry connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Sentry action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with Sentry examples; they add no Sentry capability - Sentry is not an event source, a trigger cannot read Sentry data, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe).
Host static files on subdomains with optional authentication. Use when you need to serve HTML, images, CSS, JS, or any static content on a dedicated subdomain. Supports file upload, basic auth, quota management, and automatic SSL via Caddy. Commands include sf sites (create/list/delete), sf upload (files/directories), sf files (list/delete).
Download YouTube videos by URL in various resolutions using a pay-per-use API with credit-based authentication and no charge on failed downloads.