app
Adom Google
Public Made by Adomby adom
Drive your whole Google Workspace from the terminal, run by your AI. Read Gmail, write Google Docs, build Google Sheets and Google Slides, search Google Drive, manage Google Calendar and Google Tasks, and post to Google Chat, plus any Google API and a zero-setup personal Gmail.
← Commit history
Surface Google Chat DMs as THE private user-ping channel: brief + discovery triggers (gchat me, dm me, ping me, message me) + READ-FIRST section, so agents find chat send --to <email> instead of posting to team webhook spaces.
2 files changed
+25−3
SKILL.md+10−1@@ -1,10 +1,19 @@ --- name: adom-google-description: "Programmatic read+write access to a user's WHOLE Google Workspace — Gmail, Contacts, Drive, Sheets, Docs, Slides, Calendar, Tasks, Google Chat — plus a generic `api` passthrough to hit ANY Google API. CLI + OAuth only (no browser automation). Public/open-source; used daily by the Adom team. Auth is the account-specific part — Adom employees use it out of the box; other orgs either self-host their own OAuth gateway or email [email protected] for a managed OAuth container (~$5/mo). First run just authorizes with FULL Workspace access (no mode question to ask the user). Use when setting up/installing adom-google, authorizing Google, reading Gmail attachments/.ics, creating/listing/searching Contacts, editing Sheets/Docs/Slides, Drive files, Calendar events, posting to Google Chat, or any Google Workspace automation. For a brand-new ORG that needs its own Google OAuth client (non-Adom team getting started), use the companion `adom-google-onboarding` skill — it drives the user's real browser through Google Cloud Console and auto-configures everything. Trigger words — adom-google, install adom-google, set up adom-google, configure adom-google, google workspace cli, edit google sheet/doc/slides, drive upload, calendar event, post to google chat, post to chat as me, message colby, send a chat, dm <person>, gmail attachment, google contacts, people api, full workspace access, google oauth gateway broker, google api passthrough, self-host oauth, managed oauth container, onboard my org to google, set up google workspace for my company/team, configure google oauth for <org>, get my company on adom-google, create our google cloud oauth client."+description: "Programmatic read+write access to a user's WHOLE Google Workspace — Gmail, Contacts, Drive, Sheets, Docs, Slides, Calendar, Tasks, Google Chat — plus a generic `api` passthrough to hit ANY Google API. CLI + OAuth only (no browser automation). Public/open-source; used daily by the Adom team. Auth is the account-specific part — Adom employees use it out of the box; other orgs either self-host their own OAuth gateway or email [email protected] for a managed OAuth container (~$5/mo). First run just authorizes with FULL Workspace access (no mode question to ask the user). Use when setting up/installing adom-google, authorizing Google, reading Gmail attachments/.ics, creating/listing/searching Contacts, editing Sheets/Docs/Slides, Drive files, Calendar events, posting to Google Chat, or any Google Workspace automation. For a brand-new ORG that needs its own Google OAuth client (non-Adom team getting started), use the companion `adom-google-onboarding` skill — it drives the user's real browser through Google Cloud Console and auto-configures everything. Trigger words — gchat, gchat me, dm me, message me, ping me, notify me, private message, reach me on chat, adom-google, install adom-google, set up adom-google, configure adom-google, google workspace cli, edit google sheet/doc/slides, drive upload, calendar event, post to google chat, post to chat as me, message colby, send a chat, dm <person>, gmail attachment, google contacts, people api, full workspace access, google oauth gateway broker, google api passthrough, self-host oauth, managed oauth container, onboard my org to google, set up google workspace for my company/team, configure google oauth for <org>, get my company on adom-google, create our google cloud oauth client." --- # adom-google +## Private ping to your user (READ FIRST if you were asked to "gchat/message/ping me")++`adom-google chat send --to <their email>` resolves the user's PRIVATE DM and posts+there - only they see it. This is THE channel for personal agent-to-human messages+(status pings, "done", "need you"). Do NOT use adom-gchat's webhook spaces for+personal messages: those are team-visible (on Adom, the whole company). "gchat me"+means "reach me on Google Chat", not "post to a team space".++ One CLI for a user's Google Workspace from inside an Adom container. **REST-direct** — it calls the Google APIs straight, owns auth via the **Adom OAuth Gateway**, and stores a long-lived refresh token `0600`. No browser automation, no per-user Google Cloud project.
package.json+15−2@@ -62,7 +62,20 @@ "connect my personal gmail", "use adom-google with my personal gmail", "connect my gmail account",- "adom-google"+ "adom-google",+ "gchat",+ "gchat me",+ "google chat",+ "dm me",+ "DM the user",+ "message me",+ "ping me",+ "notify me",+ "send me a message",+ "private message",+ "message the user privately",+ "reach me on chat",+ "chat me" ], "dependencies": {}, "scripts": {@@ -107,5 +120,5 @@ "prompt": "post to Google Chat that the boards shipped" } ],- "brief": "Drive your whole Google Workspace from the terminal, run by your AI. Gmail, Drive, Sheets, Docs, Slides, Calendar, Tasks, and Chat, plus any Google API and a personal Gmail with zero setup."+ "brief": "Drive your whole Google Workspace from the terminal, run by your AI. Google Chat DMs (THE private channel for pinging your user: chat send --to <email>), Gmail, Drive, Sheets, Docs, Slides, Calendar, Contacts, plus a raw API passthrough." }