Can design automation for live browsers, accounts, workflows, or infrastructure; use staging targets and human approval before destructive or account-write actions., Keep API tokens and service credentials least-privileged, and verify generated runbooks before scheduling or unattended execution.
Privacy notes
Inputs and outputs can include browser state, account metadata, workflow payloads, infrastructure inventory, logs, and operational screenshots., Redact credentials, session data, customer records, internal hostnames, and private workspace details before sharing prompts or artifacts.
Current risk score 0/100. Use staged verification before broader rollout.
Risk 0
Pre-adoption checks
Validate source and review signals before any execution.
Confirm source provenanceRequired
Source URL/provenance metadata is present.
Done
Confirm metadata review state
Listing has review metadata.
Done
Verify install payload
Install/config payload exists and can be inspected.
Done
Security checks
Confirm safety, privacy, and package integrity signals.
Review safety notesRequired
Safety notes are present.
Done
Review privacy notesRequired
Privacy notes are present.
Done
Verify package integrity metadata
Package verification/checksum metadata is available.
Done
Rollout
Adopt in controlled steps based on the selected plan.
Run in isolated sandbox firstRequired
Use a constrained sandbox and observe behavior across multiple tasks.
Pending
Roll out graduallyRequired
Roll out to a small cohort before wider usage.
Pending
Set monitoring and fallback
Define rollback path and monitor errors after adoption.
Pending
Evidence readiness
Evidence readiness matrix · balanced
Required evidence gates are covered (6/6 signals complete).
Risk 0
Source provenance
Present
Source repository/provenance is listed.
Required in this preset
Metadata review
Present
Review metadata is present.
Required in this preset
Safety notes
Present
Safety notes are present.
Required in this preset
Privacy notes
Present
Privacy notes are present.
Optional in this preset
Package integrity
Present
Package integrity metadata is present.
Optional in this preset
Install payload
Present
Install payload is available.
Required in this preset
Required evidence gates are covered for this preset.
Decision timeline
Decision timeline · balanced
6/6 steps complete with no blocking gaps for this preset.
Risk 0
triage
Confirm source provenanceRequired
Source/provenance metadata is available.
Done
triage
Check metadata review statusRequired
Review metadata is available.
Done
verify
Review safety notesRequired
Safety notes are available.
Done
verify
Review privacy notes
Privacy notes are available.
Done
verify
Validate package integrity metadata
Package integrity metadata is available.
Done
rollout
Verify install payload and commandsRequired
Install payload is available.
Done
No required blockers for this timeline preset.
Prerequisite readiness
Prerequisite readiness
3 prerequisites to line up before setup. Have accounts and credentials ready first.
0/3 ready
Account & credentials2General1
Safety & privacy surface
Safety & privacy surface
2 safety and 2 privacy notes across 3 risk areas. Review closely: credentials & tokens.
3 areas
SafetyExecution & processesCan design automation for live browsers, accounts, workflows, or infrastructure; use staging targets and human approval before destructive or account-write actions.
SafetyCredentials & tokensKeep API tokens and service credentials least-privileged, and verify generated runbooks before scheduling or unattended execution.
PrivacyData retentionInputs and outputs can include browser state, account metadata, workflow payloads, infrastructure inventory, logs, and operational screenshots.
PrivacyCredentials & tokensRedact credentials, session data, customer records, internal hostnames, and private workspace details before sharing prompts or artifacts.
Safety notes
Can design automation for live browsers, accounts, workflows, or infrastructure; use staging targets and human approval before destructive or account-write actions.
Keep API tokens and service credentials least-privileged, and verify generated runbooks before scheduling or unattended execution.
Privacy notes
Inputs and outputs can include browser state, account metadata, workflow payloads, infrastructure inventory, logs, and operational screenshots.
Redact credentials, session data, customer records, internal hostnames, and private workspace details before sharing prompts or artifacts.
Prerequisites
Access to Google Workspace resources
Gemini API or platform integration credentials
Target business workflow with measurable success criteria
.gemini/skills/<skill-name>/SKILL.md or .agents/skills/<skill-name>/SKILL.md
cursor
Adapter
.cursor/rules/<skill-name>.mdc
cli
Manual
AGENTS.md or tool-specific context file
Full copyable content
# Trigger
"Apply the Google Workspace Gemini automation skill to this process."
# Required output
1) Automation architecture and data flow
2) Prompt/template design with quality checks
3) Approval and exception handling
4) Monitoring and cost controls
About this resource
Overview
This skill helps AI agents build practical Google Workspace automations using Gemini. It focuses on workflows teams actually run: reporting, triage, routing, summarization, and structured content generation.
Compatibility
Native
Claude Code / Claude: native skill usage via SKILL.md.
Codex/OpenAI workflows: compatible with Agent Skills-style SKILL.md content as reusable workflow instructions.
Manual Adaptation
Gemini CLI: native skill usage via .gemini/skills/<skill-name>/SKILL.md or .agents/skills/<skill-name>/SKILL.md where supported.
Cursor: use the generated .cursor/rules/*.mdc adapter for project rules.
OpenClaw and similar agents: use the same skill content as a reusable prompt/workflow file when native skill import is unavailable.
Prerequisites
Defined source systems and destination artifacts
Data classification and privacy constraints
Human reviewers for quality-sensitive outputs
What This Skill Delivers
Workflow decomposition for Docs/Sheets/Gmail/Drive tasks
Prompt and schema patterns for reliable output structure
Quality gates and approval loops
Monitoring plan for failures, drift, and cost anomalies
How to Use This Skill
Map workflow trigger, inputs, and output destination.
Define target schema for generated content.
Add policy checks for sensitive data.
Add human review for high-impact decisions.
Track execution outcomes and iterate prompts safely.
Troubleshooting
Issue: Output quality varies by run Fix: Tighten schema constraints and add post-generation validation checks.
Issue: Automation creates noisy or irrelevant docs Fix: Refine source filtering and enforce clear acceptance criteria.
Issue: Costs rise unexpectedly Fix: Add workload bucketing and caching for repeat context segments.
Knowledge Freshness
Treat tooling details as time-sensitive. Re-validate APIs, limits, pricing, auth models, and deployment flags immediately before implementation. If docs conflict with prior memory, follow current official docs and release notes.
Show that Google Workspace Gemini Automation Skill is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/skills/google-workspace-gemini-automation)
How it compares
Google Workspace Gemini Automation Skill side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
2 trust signals differ across this comparison (Package trust, Source provenance).
Google Agents CLI skill suite for coding agents that build, scaffold, evaluate, deploy, publish, and observe ADK agents on Gemini Enterprise Agent Platform, Agent Runtime, Cloud Run, GKE, and Google Cloud.
Google Agent Skills catalog for AI agents working with Google Cloud, Gemini Enterprise Agent Platform, Gemini APIs, Skill Registry, Cloud Run, BigQuery, Firebase, GKE, Cloud SQL, AlloyDB, gcloud, auth, onboarding, and Well-Architected Framework guidance.
✓Can design automation for live browsers, accounts, workflows, or infrastructure; use staging targets and human approval before destructive or account-write actions.
Keep API tokens and service credentials least-privileged, and verify generated runbooks before scheduling or unattended execution.
✓Can design automation for live browsers, accounts, workflows, or infrastructure; use staging targets and human approval before destructive or account-write actions.
Keep API tokens and service credentials least-privileged, and verify generated runbooks before scheduling or unattended execution.
✓The skills intentionally guide agents through scaffold, eval, deploy, publish, CI/CD, infrastructure, datastore, and observability workflows that can create or modify cloud resources.
Deployment and infrastructure commands may provision service accounts, IAM bindings, Terraform resources, Cloud Run services, Agent Runtime deployments, GKE resources, Artifact Registry images, Secret Manager entries, and CI/CD runners.
The workflow skill explicitly requires clarifying goals and writing a spec before scaffolding a new project; skipping that step can create wrong infrastructure or unsafe agent behavior.
Evaluation guidance may invoke LLM-as-judge, synthetic datasets, and prompt optimization; treat cost, data exposure, and nondeterminism as production concerns.
Do not run deploy, publish, infrastructure, datastore, or CI/CD commands without explicit human approval and a known Google Cloud target.
✓Google Cloud skills can create, update, delete, deploy, query, or configure cloud resources, datasets, IAM policies, service accounts, APIs, containers, jobs, and networking.
The gcloud skill requires command validation and safety guardrails before invoking Google Cloud CLI commands; do not let agents improvise cloud commands from memory.
Skill Registry guidance includes skill lifecycle management such as upload, update, and permanent delete operations; validate environment and approval before use.
Cloud Run, GKE, BigQuery, Firebase, Cloud SQL, AlloyDB, and Gemini API workflows can create cost, expose endpoints, alter data, or change production behavior.
The repository notes active development, so verify exact commands, product names, API availability, and launch-stage limits before production use.
Privacy notes
✓Inputs and outputs can include browser state, account metadata, workflow payloads, infrastructure inventory, logs, and operational screenshots.
Redact credentials, session data, customer records, internal hostnames, and private workspace details before sharing prompts or artifacts.
✓Inputs and outputs can include browser state, account metadata, workflow payloads, infrastructure inventory, logs, and operational screenshots.
Redact credentials, session data, customer records, internal hostnames, and private workspace details before sharing prompts or artifacts.
✓Agents CLI projects can contain Google Cloud credentials, AI Studio keys, Secret Manager names, service account emails, project IDs, regions, Terraform state, eval traces, prompts, tool outputs, logs, traces, user data, embeddings, and datastore contents.
Eval artifacts and observability exports can include full prompts, tool calls, responses, failure rationales, trace IDs, and private application data.
Publishing to Gemini Enterprise, deploying to Agent Runtime, Cloud Run, or GKE, and enabling analytics can move agent traffic into Google Cloud services subject to separate terms and access controls.
Keep project IDs, credentials, Terraform state, traces, eval datasets, user data, private prompts, and secret names out of public issues, PRs, examples, and screenshots.
✓Google Cloud workflows may expose project IDs, service account emails, OAuth tokens, API keys, ADC credentials, Terraform state, dataset names, table schemas, query text, logs, traces, prompts, model outputs, embeddings, and customer data.
BigQuery, Firebase, Cloud SQL, AlloyDB, GKE, and Agent Platform workflows may process regulated or proprietary data; review data residency, IAM, retention, audit logging, and sharing rules before use.
Gemini API and Agent Platform skills can send prompts, files, images, audio, video, tool inputs, structured outputs, cached contexts, and batch datasets to Google services.
Keep credentials, project IDs when sensitive, private queries, logs, trace payloads, Terraform state, customer data, and generated datasets out of public prompts, issues, PRs, and screenshots.
Prerequisites
Access to Google Workspace resources
Gemini API or platform integration credentials
Target business workflow with measurable success criteria
Target web workflow with clear start and success states
Ability to run browser automation in local or CI environment
Access to auth/session strategy if login is required
Coding assistant or skill host that can consume Agent Skills, or a local terminal where `uvx google-agents-cli setup` can install the CLI plus skills.
Python 3.11+, uv, and Node.js for the documented setup flow.
Google Cloud project, billing, credentials, APIs, IAM, region, and deployment target decisions when moving beyond local development.
Clear agent requirements before scaffolding: purpose, external APIs, tools, safety constraints, data sources, and deployment preference.
AI coding assistant or skill host compatible with the Agent Skills standard and the skills CLI.
Google Cloud project, credentials, billing, enabled APIs, IAM roles, and target region when a selected skill touches cloud resources.
Current gcloud, bq, kubectl, Terraform, SDK, or product-specific tooling required by the selected Google Cloud workflow.
Clear approval boundary before any agent runs cloud deployment, IAM, data, billing, registry, or destructive operations.