Google Workspace — Gmail, Calendar, Drive, Docs, Sheets via gws CLI or Python
Google Workspace — Gmail, Calendar, Drive, Docs, Sheets via gws CLI or Python
Start with meaning, then move to detail.
This lesson explains Google Workspace — Gmail, Calendar, Drive, Docs, Sheets via gws CLI or Python as part of operating Hermes with explicit security boundaries. You will learn what it does, when it matters, and the smallest safe test that proves it works.
If you are new, do not memorize names. Focus on three questions: what problem does this solve, what access does it need, and how can you verify the result?
For practice, inspect the first example, identify its effects, run it on test data, and compare the result with the source claim.
For advanced readers, inspect Skill metadata, Reference: full SKILL.md, References, then verify failure modes and version compatibility.
You only need to know which files and accounts the agent may access.
A clear outcome before you read.
- Understand Google Workspace — Gmail, Calendar, Drive, Docs, Sheets via gws CLI or Python without assumed prior knowledge.
- Separate the source description from what still needs testing in your environment.
- Read the first command and identify its inputs and outputs before copying it.
Short definitions before the details.
- Skill
- An instruction bundle that teaches Hermes a repeatable workflow without necessarily adding an external service.
Gmail, Calendar, Drive, Docs, Sheets via gws CLI or Python
What does the source say, and in what order?
- 01Skill metadata
Start here to understand the core idea or structure.
- 02Reference: full SKILL.md
Read this after the foundation, then connect it to the previous step.
- 03References
Read this after the foundation, then connect it to the previous step.
- 04Scripts
Read this after the foundation, then connect it to the previous step.
- 05First-Time Setup
Read this after the foundation, then connect it to the previous step.
- 06Step 0: Check if already set up
Read this after the foundation, then connect it to the previous step.
- 07Step 1: Triage — ask the user what they need
Read this after the foundation, then connect it to the previous step.
- 08Step 2: Create OAuth credentials (one-time, ~5 minutes)
Read this after the foundation, then connect it to the previous step.
- 09Step 3: Get authorization URL
Read this after the foundation, then connect it to the previous step.
- 10Step 4: Exchange the code
Finish here to verify the result and special cases.
Copy only after you understand the effect.
GSETUP="python ${HERMES_HOME:-$HOME/.hermes}/skills/productivity/google-workspace/scripts/setup.py"$GSETUP --check$GSETUP --client-secret /path/to/client_secret.jsonRead the first command and identify its inputs and outputs before copying it.
Match every command to your installed Hermes version, review the files and accounts it can reach, and use non-sensitive data for the first test. If this explanation differs from the source, the official source wins.