القائمة
Triage Gmail inbox — surface Google Doc mentions, calendar invites, and important emails while filtering noise
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | gmail-triage |
| description | Triage Gmail inbox — surface Google Doc mentions, calendar invites, and important emails while filtering noise |
| tags | ["gmail","triage","productivity"] |
| user_invocable | true |
Scan unread Gmail, classify messages, and present what matters — Google Doc activity, calendar invites, direct emails — while filtering Jira, sales, newsletters, and other noise.
Run these two gws commands in parallel:
Query A — Main inbox scan:
gws gmail +triage --query 'is:unread -from:<<JIRA_BOT_EMAIL>> -label:CATEGORY_PROMOTIONS -label:CATEGORY_SOCIAL' --max 50 --format json --labels
Query B — Google Docs notifications (catch miscategorized):
gws gmail +triage --query 'is:unread from:(*@google.com) subject:(commented OR shared OR mentioned OR assigned)' --max 20 --format json
Merge results and deduplicate by message id.
Use sender + subject + labels only (no body fetch). Apply rules from docs/classification-rules.md in order — first match wins:
| Category | Description |
|---|---|
GOOGLE_DOCS | Doc/Sheet/Slide mentions, comments, shares |
CALENDAR | Event invitations, updates, RSVPs |
INTERNAL | From @<<ORG_DOMAIN>>, not docs/cal/jira |
EXTERNAL_IMPORTANT | External sender, appears directed at <<USER_NAME>> |
SKIP | Jira, sales, restaurant, newsletter, automated noise |
Only for EXTERNAL_IMPORTANT messages where sender+subject aren't conclusive:
gws gmail users messages get --params '{"userId": "me", "id": "<message_id>"}' --format json
Check for: unsubscribe links, marketing boilerplate, sales pitch language (demo, free trial, pricing, quick question). Reclassify to SKIP if detected. Max 10 fetches.
Output in this order:
Summary line:
Inbox triage (YYYY-MM-DD): X scanned, Y surfaced, Z filtered
Google Docs Activity (if any):
| Document | Action | From | Time |
|---|
Calendar Invites (if any):
| Event | From | When | Status |
|---|
Direct Emails — Internal (if any):
| From | Subject | Time |
|---|
Direct Emails — External (if any):
| From | Subject | Time |
|---|
Filtered: N messages filtered (Jira, promotions, automated). Say "show filtered" to see them.
After presenting results, offer:
gws gmail +triage returns id, threadId, snippet, from, to, subject, date, labelsgws gmail users messages get --params '{"userId": "me", "id": "..."}' --format json returns full message<<ORG_DOMAIN>><<USER_EMAIL>>Print a document to the default printer. Accepts a markdown file (vault path or shorthand), a Google Docs URL, a Google Slides URL, a Google Drive file URL, or any local PDF. Markdown is rendered via pandoc + Chrome headless; Google Workspace files are exported as PDF via gws. Triggered by "print this", "print today's daily", "print [file]", "print this gdoc", "send to printer", or any request to put a doc on paper.
Pull today's Obsidian daily notes, extract themes, and ask follow-ups to help get started. Triggered by "pull today's notes", "daily notes", "what did I dictate today", "check my notes", "morning review", "obsidian notes".
Take a raw source file (synced Confluence page, Google Doc, Zoom note, or pasted article) and integrate its content into <<USER_NAME>>'s Obsidian wiki layer — updating relevant project/people/team pages with cross-references, deltas, and new context. Append an entry to log.md. Triggered by "integrate this into the wiki", "fold X into the wiki", "/integrate", "process this source", "absorb this into the vault".
Bulk sync Superwhisper meeting recordings to the Obsidian vault. Scans recordings for a date, matches each to a Google Calendar event for title + attendees, writes detailed notes to zoom/ and structured summaries to the daily note. Use when the user says "sync my meetings", "pull meeting notes", "sync today's meetings", "backfill meetings", "sync yesterday's meetings", or wants meeting transcripts retroactively processed into the vault. (Renamed from granola-sync 2026-05-07; the old Granola-based flow is gone — this skill replaces it.)
Check Slack DMs (1-on-1 and group), and public/private channel mentions for conversations still waiting on <<USER_NAME>>'s reply. Surfaces "on read" messages where someone messaged or @-mentioned <<USER_NAME>> but he never responded. Use this skill whenever the user says "catch up on Slack", "check my Slack", "am I on read", "did I miss anything", "unanswered messages", "dangling threads", "Slack backlog", "who's waiting on me", or any variation of checking for unread/unreplied Slack messages. Also use when the user asks about DMs, group DMs, or mentions from a specific time range.
Install, troubleshoot, or retrigger <<USER_NAME>>'s Zoom → Superwhisper → Obsidian → Claude transcription pipeline. Use when the user says "set up zoom transcription", "fix zoom transcripts", "why didn't my zoom get transcribed", "check transcript log", "retrigger that transcript", "my last meeting didn't save", "reinstall zoom automation", or anything that sounds like debugging or rebuilding the automated meeting-note pipeline.