← Commit history

WHICH TOOL: document the self-DM caveat + fallbacks (email, one-time 'message yourself' activation) so a failed DM never becomes a team-space post.

John Lauer ·1c1e1b55c5 ·2mo ago ·parent f35febd
2 files changed +6−4
README.md+3−2
@@ -12,8 +12,9 @@ ENTIRE COMPANY. Decide by audience, not by tool name:   private DM; only they see it. That applies even when the user says "gchat me":   they mean "reach me on Google Chat", not "post to a team space". - No private channel configured? That is NEVER a reason to post to a team space.-  Use `adom-google` (auto-resolves DMs with zero setup) or tell the user you have-  no private channel, but do not broadcast.+  Use `adom-google` (resolves DMs; note a SELF-DM needs the user to have opened+  "message yourself" once in Chat - if it says "no DM/space found", fall back to+  `adom-google gmail send` to their email, or ask them in-session), but do not broadcast.  Post messages to Google Chat spaces from any Adom container. Webhook-based, no OAuth needed. Each org customizes it for their own Google Workspace, then
SKILL.md+3−2
@@ -24,8 +24,9 @@ ENTIRE COMPANY. Decide by audience, not by tool name:   private DM; only they see it. That applies even when the user says "gchat me":   they mean "reach me on Google Chat", not "post to a team space". - No private channel configured? That is NEVER a reason to post to a team space.-  Use `adom-google` (auto-resolves DMs with zero setup) or tell the user you have-  no private channel, but do not broadcast.+  Use `adom-google` (resolves DMs; note a SELF-DM needs the user to have opened+  "message yourself" once in Chat - if it says "no DM/space found", fall back to+  `adom-google gmail send` to their email, or ask them in-session), but do not broadcast.  Post messages to Google Chat spaces from any Adom container. Webhook- based, no OAuth needed. Each org customizes it for their own Google