check-email — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited check-email (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Use the mailbridge MCP tools to fetch and present emails.
Call read_emails with folder (default: INBOX) and limit (default: 10).
Each email now includes priority (1–5) and category fields — surface these when useful:
Present results as a numbered list:
1. 🔴 [From] Subject — Date (priority 5)
2. [From] Subject — DateIf the user wants the body of a specific email, call get_email_body with its uid. Display the body cleanly — strip excessive whitespace, preserve paragraph breaks.
If the user mentions a sender name, keyword, or subject, call search_emails with a query. After getting UIDs back, offer to fetch the full body of any result.
When the user says "show the full thread", "see the whole conversation", or "what's the context":
get_thread with the email uid and folder **Thread — [Subject]** ([N] messages)
📩 [From] · [Date]
[Preview...]
📩 [From] · [Date]
[Preview...]When the user asks "what's the history with [person]", "show emails from/to [contact]", or "have I emailed X before":
get_contact_history with the contact's addressWhen the user asks "any events in this?", "what's the date of this meeting?", or "add this to my calendar":
extract_calendar_events with the uid and folder 📅 **[Event Title]**
Start: [date/time]
Location: [location]set_reminderWhen the user says "export this", "save this as markdown", "give me a clean copy":
export_email with uid and folderAlways follow this flow — never skip the scan step:
Step 1 — Scan first, always Call get_attachments with the email UID. This scans and lists attachments without downloading anything.
Present the results to the user clearly:
📎 This email has 2 attachment(s):
1. report.pdf — 340 KB · ✅ Safe
2. invoice.docx — 80 KB · ✅ SafeIf any attachment shows ⚠️ Warning or 🚫 Blocked, tell the user:
"⚠️ [filename] looks suspicious — [safety_note]. I won't download this one."
Never call read_attachment on a blocked file.
Step 2 — Ask for permission After showing the scan results, ask:
"Would you like me to open any of these?"
Wait for the user to say yes and specify which one before calling read_attachment.
Step 3 — Download and read (after user confirms) Call read_attachment with the approved part_id. The assistant may also show a permission prompt at this step.
saved_to file path to it. If no, say: "I've saved the file locally — connect a transcription plugin and I can read it for you."If any tool returns "No email account connected", respond:
"Your email isn't connected yet. Want me to open the setup so you can connect it? It only takes a moment."
If they say yes, call open_setup.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.