mail-meetings
Skill7 starsChanged 9 months agoMITView on GitHub
Find meeting invites, calendar events, and meeting-related emails (notes, agendas, reschedules). Use when user asks about meetings in their email, upcoming invites, or wants to see meeting notes. Arguments: optional time range or "upcoming", "today", "this week".
In this repository32 other files it gives its agents.
- calendar-accountsSkill
- calendar-attendeesSkill
- calendar-conflictsSkill
- calendar-coreSkill
- calendar-eventSkill
- calendar-freeSkill
- calendar-recurringSkill
- calendar-searchSkill
- calendar-statsSkill
- calendar-todaySkill
- calendar-upcomingSkill
- mail-accountsSkill
- mail-action-itemsSkill
- mail-attachmentsSkill
- mail-bankingSkill
- mail-contactsSkill
- mail-coreSkill
- mail-digestSkill
- mail-expensesSkill
- mail-fromSkill
- mail-needs-replySkill
- mail-newsletterSkill
- mail-readSkill
- mail-searchSkill
- mail-securitySkill
- mail-statsSkill
- mail-subscriptionsSkill
- mail-threadSkill
- mail-top-sendersSkill
- mail-travelSkill
- mail-triageSkill
- mail-workSkill
The file
Files
Mail Meetings — Calendar Invites and Meeting Emails
Period: $ARGUMENTS (default: last 7 days)
Query
DB="$HOME/Library/Mail/V10/MailData/Envelope Index"
SINCE=$(($(date +%s) - 604800)) # 7 days; adjust per $ARGUMENTS
sqlite3 "$DB" "
SELECT datetime(m.date_received,'unixepoch','localtime') as dt,
s.subject, a.address as sender, a.comment as name,
mb.url as mailbox, m.ROWID, m.read
FROM messages m
JOIN subjects s ON m.subject = s.ROWID
JOIN addresses a ON m.sender = a.ROWID
JOIN mailboxes mb ON m.mailbox = mb.ROWID
WHERE m.date_received >= ${SINCE}
AND m.deleted = 0
AND mb.url NOT LIKE '%Spam%' AND mb.url NOT LIKE '%Trash%'
AND (
s.subject LIKE '%invitation%'
OR s.subject LIKE '%invite%'
OR s.subject LIKE '%meeting%'
OR s.subject LIKE '%standup%'
OR s.subject LIKE '%retro%'
OR s.subject LIKE '%sync%'
OR s.subject LIKE '%call%'
OR s.subject LIKE '%agenda%'
OR s.subject LIKE '%(Updated invitation)%'
OR s.subject LIKE '%has invited you%'
OR s.subject LIKE '%calendar%'
OR s.subject LIKE '%@ %'
OR a.address LIKE '%calendar%'
OR a.address LIKE '%gemini-notes%'
OR a.address LIKE '%meet-recordings%'
)
ORDER BY m.date_received DESC;" 2>/dev/nullStep 2: Categorize meeting emails
Parse bodies to extract:
- New invites: "You have been invited to..." — extract meeting title, date/time, organizer
- Updated invites: time or attendee changes
- Cancelled meetings: "has been cancelled"
- Meeting notes/summaries: from Gemini Notes, Otter.ai, Notion, etc.
- Agendas: ahead of meetings
python3 ~/.claude/skills/_mail-shared/parser.py <ROWID1> <ROWID2> ...Step 3: For upcoming meetings, extract key fields
From invite body, find:
- Meeting title
- Date and time (look for
@,on [date], time patterns) - Organizer
- Video link (Zoom, Google Meet, Teams URLs)
- Location
Output Format
Group by type:
Upcoming Meetings (invites received):
| Meeting | When | Organizer | Link |
Updated/Changed Meetings: [list changes]
Meeting Notes received: [list summaries with key decisions/action items extracted]
Cancelled: [list cancellations]
For each meeting note, pull out "Suggested next steps" or "Action items" sections if present.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

