ClawHub

Openclaw Email Orientation

v1.0.1

Explain how email and Google Calendar work for OpenClaw agents, including the distinction between agent email and owner email, how gog and the Google Workspa...

⭐ 0· 58·1 current·1 all-time
byNetanel Abergel@netanel-abergel
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
The skill's name and description match the SKILL.md content: it's an orientation/troubleshooting guide for agent vs owner email and using gog to access Gmail/Calendar. It does not ask for unrelated credentials, binaries, or installs.
✓
Instruction Scope
Instructions are limited to explanation and CLI examples for gog, account distinction, OAuth flows, calendar sharing steps, and troubleshooting checks. It references sensitive local paths (e.g., ~/.openclaw/.gog/credentials.json) but explicitly instructs not to print their contents — this is appropriate for an orientation guide.
✓
Install Mechanism
No install spec or code is included (instruction-only). No downloads, extracted artifacts, or package installs are requested.
ℹ
Credentials
The skill requires no declared environment variables or credentials; it does reference using GOG_ACCOUNT when running gog commands and points to local credential files. The references are proportional to the topic, but users should understand those files contain sensitive OAuth credentials and should not be shared.
✓
Persistence & Privilege
The skill is not always-enabled and does not request elevated or persistent system privileges. It does not modify other skills or system-wide settings.
Assessment
This skill is a readable how-to for setting up agent access to Gmail and Calendar and appears coherent. Before installing or using it, ensure you: (1) understand the distinction between the human "owner" account and any agent account and only grant the agent the minimum calendar permissions needed; (2) keep the referenced files (e.g., ~/.openclaw/.gog/credentials.json and auth-profiles.json) private — do not paste their contents into chat; and (3) only run gog commands you trust on machines you control. There are no hidden installs or unexpected network endpoints in this skill, but the instructions do involve OAuth credentials and consent flows — handle those secrets the same way you would for any Google API client.

Like a lobster shell, security has layers — review code before you run it.

latestvk9794p0f0ke9d2q680eempk94h8431bz

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments