skills.rest
tomspiegl
tomspieglCOMMUNITY
Explore all skills by this author →
GitHub

hetzbot-google

Deploy shared Google API credentials for Gmail, Drive, and Sheets across fleet hosts.

Updated Apr 17, 2026
Search Tags:#automation#devops#credentials#oauth2#google-api#fleet
One-click install
npx skills add https://github.com/tomspiegl/hetzbot --skill hetzbot-google
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hetzbot-google
Source: https://github.com/tomspiegl/hetzbot/tree/main/skills/infra/google
Command: npx skills add https://github.com/tomspiegl/hetzbot --skill hetzbot-google

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires google-auth, google-auth-oauthlib, google-api-python-client.

What problem does it solve?

Centralizes and secures Google API access for fleet services by providing a single credential set and automated deployment workflow, eliminating local secret sprawl.

Core Features & Use Cases

  • Centralized Google API credentials for Gmail, Drive, and Sheets across all fleet hosts.
  • OAuth2 consent flow on the operator laptop with token lifecycle management.
  • Secure deployment to hosts under /etc/hetzbot/google and automatic verification.

Quick Start

Deploy Google credentials to the fleet hosts and verify access by sending a test Gmail message.

Frequently Asked Questions about hetzbot-google

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

FAQPage Schema
How do I share Google API credentials across multiple fleet hosts?▼

Sharing Google API credentials across fleet hosts requires centralizing a single OAuth2 credential set and deploying it automatically to each host. This eliminates local secret sprawl while securely provisioning tokens for Gmail, Drive, and Sheets access.

What is the best way to manage OAuth2 token lifecycle for fleet services?▼

Managing OAuth2 token lifecycle for fleet services involves running the consent flow on an operator laptop and enforcing automated token distribution. This ensures secure deployment and ongoing verification across all fleet hosts.

How do I deploy Google API credentials to remote hosts and verify access?▼

Deploying Google API credentials to remote hosts involves securely distributing tokens to a specific directory like /etc/hetzbot/google. You can verify access by sending a test Gmail message to confirm successful provisioning.

Does this approach support Gmail, Drive, and Sheets automation?▼

Yes, this centralized approach supports Gmail, Drive, and Sheets automation. It provides a shared credential set across all fleet hosts, allowing automated services to securely access these Google APIs without local secret sprawl.

Do I need google-auth and google-api-python-client to manage fleet credentials?▼

Yes, you need google-auth, google-auth-oauthlib, and google-api-python-client. These dependencies provide the necessary OAuth2 consent flow and API client interfaces to provision and distribute tokens across your fleet.

Why does centralizing Google API access help prevent local secret sprawl?▼

Centralizing Google API access prevents local secret sprawl by replacing individual host credentials with a single shared set. This enforces end-to-end credential provisioning and secure token distribution to eliminate scattered local secrets.

Related Skills

Explore More Software Engineering Skills→
ToqsickToqsick

google-oauth-setup

Automate Google Workspace API OAuth2 setup with client secret and consent screen configuration.

Community
Intermediate
wangqianCAIwangqianCAI

gog

Manage Gmail, Calendar, Drive, Sheets, and Docs via a unified command-line interface.

Community
Intermediate
mozilor-technologiesmozilor-technologies

vercel-cli-with-tokens

Manage Vercel tokens, project linking, deployments, and environments via CLI.

Official
Intermediate
dededeclinedededecline
2

1password

Automate secret management with the 1Password CLI for vaults, items, and injection.

Community
Advanced