mail-transcripts
Skill166 starsChanged 5 months agoMITView on GitHub
Gmail AI transcript notifications → meeting Notes: URLs + mark read. Args: (none). Invoked standalone or as step 1 of /meeting wrap.
In this repository29 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .agents/skills/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/qmd-search.mdcCursor rule
- .cursor/rules/skill-conventions.mdcCursor rule
- .cursor/rules/skill-registry.mdcCursor rule
- cache-notesSkill
- commitSkill
- defuddleSkill
- fill-participantsSkill
- followup-todosSkill
- json-canvasSkill
- last-1on1Skill
- meetingSkill
- migrate-tagsSkill
- note-statusSkill
- obsidian-basesSkill
- obsidian-cliSkill
- obsidian-markdownSkill
- onboard-personSkill
- organize-meetingsSkill
- otter-fetchSkill
- people-stubsSkill
- qmdSkill
- recapSkill
- sprint-retroSkill
- sync-upstream-obsidianosSkill
- vault-healthSkill
- workspace-modeSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 73
When /mail-transcripts is run standalone, offer /commit.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Mail Transcripts
Setup: SETUP.md — Gmail label, OAuth scopes, and
resolve_path()customization.
Usage
/mail-transcripts— Run the Gmail → vault sync once (no arguments).
When to run
| Caller | When |
| Standalone | Whenever you want to drain the AI-transcript inbox without wrapping meetings. |
/meeting wrap <path> | Step 1 — Before /cache-notes, so Notes: is filled from Gmail when Gemini emails beat manual paste. |
/meeting wrap pending … | Step 1 — Before discovering pending meetings, so newly linked or auto-created notes are included in the pending scan. |
Gmail filter
Fixed query (do not change without updating this skill and the script):
label:🤖-ai-transcripts in:inboxThe label name includes the emoji 🤖 (robot). Ensure that label exists in Gmail and that transcript notifications are delivered into Inbox with that label applied.
Workflow
Step 1: Preconditions
- Confirm
gwsis installed and authenticated (gws auth status). - Confirm Gmail OAuth includes read + modify message scopes (marking read uses
users.messages.modify).
Step 2: Run the vault script
From the vault root, run:
python3 .scripts/gmail_ai_transcripts_to_meetings.pyImplementation lives in .scripts/gmail_ai_transcripts_to_meetings.py. The script:
- Lists messages matching the query (paginated up to
maxResultsin script — currently 100). - For each message, decodes MIME parts, extracts
https://docs.google.com/document/d/...URLs. - Parses the subject line
Notes: "Title" Mon DD, YYYY(supports curly""Unicode quotes). A bareMeeting Summary for <recurring meeting>(noNotes:pattern) maps to that meeting using the emailDateheader. - Resolves
Meetings/**/*.mdtargets using title + date heuristics (daily standups →Meetings/Engineering/Scrum/YYYY-MM-DD.md, tech-leads →Meetings/Engineering/TechLeads/, interviews →Meetings/Interviews/, etc. — see scriptresolve_path()). Edit that function to match your own folder conventions. - Updates existing notes: appends the Doc URL under
Notes:if that document ID is not already present. - Creates a minimal meeting stub if no file exists (
Notes:,created:,# Title - YYYY-MM-DD) — agents may refine folder/title afterward. - Marks each processed message read by removing the
UNREADlabel viagws gmail users messages modify.
Step 3: Report
Print a short summary: created paths, updated paths, noop (URL already in note), skip_no_doc (no Doc URL in body — still marked read if the script marks those), and any errors.
Important Notes
- No Google Doc in email (e.g. narrative-only "Meeting Summary"): the script cannot set
Notes:; it may still mark the thread read — adjust script behavior there if you want to leave unread for triage. - Wrong meeting matched: resolution is heuristic; fix
resolve_path()in the script or move/rename the note in Obsidian. - Privacy: transcript emails stay in Gmail; the skill only links Docs into local vault files.
- Do not duplicate
mail-transcriptslogic in other skills — call the script or point here.
Offer to commit
When /mail-transcripts is run standalone, offer /commit. When run inside /meeting wrap or /meeting wrap pending, the parent sequence commits once at the end (include any new/updated meeting files in that commit scope).
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.

