manage-inbox — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited manage-inbox (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 organise and manage emails.
| Action | Tool | Key Parameters |
|---|---|---|
| Mark read | mark_as_read | uid, folder |
| Mark unread | mark_as_unread | uid, folder |
| Move to folder | move_email | uid, from_folder, to_folder |
| Delete (Trash) | delete_email | uid, folder |
| List folders | list_folders | — |
Use bulk tools when the user wants to act on multiple emails at once — they operate in a single IMAP operation (much faster than looping):
| Action | Tool | Key Parameters |
|---|---|---|
| Mark multiple read | bulk_mark_read | uids: [], folder |
| Mark multiple unread | bulk_mark_unread | uids: [], folder |
| Move multiple | bulk_move | uids: [], from_folder, to_folder |
| Delete multiple | bulk_delete | uids: [], folder |
Workflow for bulk:
search_emails to find matching UIDsSet a reminder on an email so it surfaces in inbox summaries when due:
| Action | Tool |
|---|---|
| Set reminder | set_reminder with uid, folder, due_date, optional note |
| View reminders | list_reminders — overdue ones are flagged |
| Mark done | complete_reminder with id |
due_date accepts: ISO timestamps, "tomorrow", "3 days", "next Monday", "2 weeks".
Example: "Remind me about this email in 3 days" → set_reminder with due_date: "3 days".
When the user says "unsubscribe from this", "stop getting emails from X", or "unsubscribe me":
unsubscribe_email with uid and folderList-Unsubscribe header and performs the action (HTTP or email)If the email has no List-Unsubscribe header, offer to reply asking to be removed.
Rules are local filters evaluated during inbox summaries to flag, categorise, or prioritise emails:
| Action | Tool |
|---|---|
| Add rule | add_rule — name, condition_field, condition_operator, condition_value, action_type, action_value |
| List rules | list_rules |
| Remove rule | remove_rule with name |
| Test rules | apply_rules with uids — dry run showing which emails would match |
Example rule: "Flag emails from [email protected] as urgent" → add_rule with condition_field: "from", condition_operator: "contains", condition_value: "[email protected]", action_type: "priority", action_value: "5"
When the user says "export this email", "save as markdown", "give me a clean version":
export_email with uid and foldersearch_emails or read_emails to identify the UID.Call list_folders with no parameters. Present as a clean list grouped by type:
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?"
If they say yes, call open_setup.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.