gmail-browser-draft
Skill9 starsChanged 37 days agoMITView on GitHub
Prepare Gmail drafts through the teammate's signed-in browser, and send approved messages with Sent readback. Never sends without a separate exact approval.
In this repository13 other files it gives its agents.
- site/llms-full.txtllms.txt
- site/llms.txtllms.txt
- checked-spreadsheet-analysisSkill
- document-to-action-itemsSkill
- google-calendar-browser-tasksSkill
- google-drive-browser-tasksSkill
- grounded-researchSkill
- meeting-action-itemsSkill
- private-team-reviewSkill
- systematic-debuggingSkill
- todoist-browser-tasksSkill
- weekly-review-planningSkill
- use-mac-appsSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use the teammate's own persistent browser profile at mail.google.com.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Gmail drafts in the teammate browser
Use the teammate's own persistent browser profile at mail.google.com. Draft preparation and sending are two separate approvals: a draft approval never authorizes Send. Single-session discipline: never copy this profile into a second browser in parallel.
- Verify the signed-in Google account matches the connected owner before acting. On any login wall, "browser may not be secure" rejection, 2FA or unexpected account, stop and request private headed sign-in. Each Google service needs its own first visit; Calendar being signed in does not imply Gmail is.
- Compose a new message: fill To, Subject and Message Body. Confirm the recipient chip before anything else. Never press Send and never use keyboard send shortcuts in this flow.
- Gmail auto-saves within seconds. Open Drafts and read the draft row back; reopen it and read To, Subject and Body values back. A row alone without reopened values is not proof.
- Discard the draft when done and verify the Drafts count drops back and the subject is gone. Verify Sent contains nothing from this flow.
- State account, recipient, subject and draft-only intent in each proposal. Touch only approved drafts. Test drafts stay private and are always discarded.
- Sending needs its own exact approval naming recipient, subject and body. Confirm the recipient chip and the filled values first. Banner overlays (for example desktop-notification prompts) can cover Send: dismiss the banner, re-snapshot for a fresh Send selector, and never click a stale one. A click that times out may still have dispatched: always read back (Sent row plus Drafts count) instead of clicking again blindly. Verify the Sent row with recipient, subject and time; delivery to the recipient inbox is confirmed by the recipient, not by Gmail.
Provenance
Sidemates maintained built-in method. Proven in a signed-in teammate browser: private self-draft composed, auto-saved (Drafts 40 to 41), reopened with all values read back, discarded (Drafts back to 40), Sent verified clean. Sending proven separately: approved message to an approved address, Sent row with recipient, subject and time read back. Instructions are bundled with Sidemates and do not grant tool or account permissions.
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.