3
GitHub Stars
3
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill krishagel/geoffrey --skill google-workspace- bun.lock16.7 KB
- package.json437 B
- SKILL.md4.9 KB
Overview
This skill provides a unified Google Workspace integration for managing email, calendar, Drive files, tasks, and chat across three accounts (work, personal, and business). It streamlines cross-account actions like forwarding messages, copying files, and syncing events. The integration exposes a set of scripts that return structured JSON and use a shared token manager for authentication. It’s built to support common Gmail search operators, calendar scheduling, Drive browsing, and simple chat posting workflows.
How this skill works
Each operation runs as a script that authenticates via a token manager tied to an account alias (psd, kh, hrg). Scripts call the relevant Google APIs (Gmail, Calendar, Drive, Tasks, Chat) and return JSON with success, data, and metadata fields. Account selection can be explicit or inferred from context; cross-account actions are supported by invoking the appropriate auth client for each target account. Errors include actionable guidance (for example, token refresh steps).
When to use it
- Manage multiple Workspace accounts without switching browser profiles
- Summarize unread mail or search messages with Gmail operators
- Schedule, update, or query calendar events across accounts
- Browse, read, create, and transfer Drive files between accounts
- Post or read chat messages and manage Google Tasks programmatically
Best practices
- Specify the account alias (psd, kh, hrg) for deterministic behavior when needed
- Use Gmail search operators to narrow results and avoid large paged queries
- Handle rate limits by retrying with exponential backoff on 429/5xx responses
- Keep OAuth refresh tokens secure and follow your organization’s allowlist requirements for the PSD account
- Store credentials in a secure secrets path and authenticate all accounts before bulk operations
Example use cases
- "Show unread psd emails" and get a top-message summary with counts
- "Schedule meeting tomorrow at 2pm" on the hrg calendar and receive the event JSON
- "Find budget spreadsheet" across Drive and open the file content for review
- "Send email from hrg with PDF attached" using the send_with_attachment flow
- "Forward this to my personal email" by copying a message from psd to kh and sending a forward
FAQ
The skill infers account contextually (work→psd, personal→kh, business/real-estate→hrg), but you can always pass an explicit alias to avoid ambiguity.
What happens when a token expires?
Tokens auto-refresh; if refresh fails you’ll receive an error JSON with a recommended command to refresh the account token.