From find-google-mentions
Find all unresolved Google Doc/Sheet/Slides comments where you are @mentioned
How this skill is triggered — by the user, by Claude, or both
Slash command
/find-google-mentions:open-comments [days] (default: 30)[days] (default: 30)The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Find all **unresolved comments that @mention me** across Google Docs, Sheets, and
Find all unresolved comments that @mention me across Google Docs, Sheets, and Slides. Surfaces threads that arrived via email notification but may have scrolled below the fold — including docs you never opened.
Time scope: $ARGUMENTS days (default to 30 if blank or not a number).
Google Drive has no "all comments mentioning me" endpoint. The workaround is
Gmail: Google sends a notification email for every @mention from
[email protected].
Search Gmail — paginate through ALL results:
from:[email protected] newer_than:{DAYS}d
Use search_gmail_messages with page_size: 25. Keep calling with the
returned page_token until no more results. Collect ALL message IDs into
a single list BEFORE fetching content.
Batch-fetch bodies — call get_gmail_messages_content_batch with
format: "full" (NEVER "metadata" — you need the body to extract links).
Use the FULL 25-per-call capacity. If you have 26+ messages, use exactly 2
calls (first 25, then the remainder). Do NOT split into smaller batches.
From each email body, extract:
docs.google.com/document/d/{ID}/...docs.google.com/spreadsheets/d/{ID}/...docs.google.com/presentation/d/{ID}/...document, spreadsheet, or presentationExtract comment-thread deep links — the notification email body contains
a direct URL to the specific comment discussion thread (the disco= parameter
URL). Capture this per-notification. The pattern is:
https://docs.google.com/{type}/d/{ID}/edit?disco={COMMENT_ID}&usp=comment_email_discussion...
This is the Link column value in the report — it takes the user straight to the thread, not just the document.
Deduplicate by document ID. You now have the unique set of docs that @mentioned you in the time window.
For each unique document, call the matching comments API:
| Doc type | Tool |
|---|---|
| document | list_document_comments |
| spreadsheet | list_spreadsheet_comments |
| presentation | list_presentation_comments |
From the returned comments, keep ONLY threads that:
[RESOLVED]Determine whether YOU have replied in each thread by checking if any reply author matches your name/email.
Present results in two sections:
Needs Your Response — unresolved threads where you have NOT replied. Sort newest first.
| # | Document | Who | What they need | Date | Link |
|---|
The Link column MUST be a clickable markdown link pointing to the comment
thread deep link (the disco= URL extracted from the notification email).
Format: [Open](https://docs.google.com/document/d/{ID}/edit?disco={COMMENT_ID}&usp=comment_email_discussion...)
If the deep link was not captured from the email, fall back to the document URL
with a #heading= or just the base document edit URL.
You Replied But Thread Still Open — unresolved threads where you DID reply but the thread remains open. May need follow-up or the other person to close it.
| # | Document | Who | Status | Date | Link |
|---|
Same Link column rules as above — always provide a clickable deep link.
End with: "Summary: X threads need your response across Y documents. Z threads are open but you already replied."
format: "full".format: "full" when fetching email content. The "metadata"
format does NOT include the body and you will have no URLs to extract.disco= URL from the email body. Pattern:
https://docs.google.com/{type}/d/{ID}/edit?disco={COMMENT_ID}&usp=comment_email_discussion...https://docs.google.com/{type}/d/{ID}/edit — this is acceptable but the
deep link is strongly preferred.[Open](url) — never bare URLs.All from the Google Workspace plugin (standard in Salesforce Claude deployments):
search_gmail_messagesget_gmail_messages_content_batchlist_document_commentslist_spreadsheet_commentslist_presentation_commentsNo additional servers or API keys needed.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Applies a firm's KYC/AML rules grid to parsed onboarding records: assigns risk rating, checks required documents, outputs rule outcomes with citations, and routes for escalation.
Generates daily or weekly digests of activity from connected sources (chat, email, docs, tasks, CRM), highlighting action items, decisions, mentions, and project updates.
npx claudepluginhub bgaldino/find-google-mentions --plugin find-google-mentions