More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Email Manager: Inbox Triage and Sending Workflows

    1

    Run any standard mailbox as a workflow over IMAP and SMTP: header-first triage with written rules, safe attachment handling, and sends that are test-sent and logged.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Email Manager: Inbox Triage and Sending Workflows

    Email Manager: Inbox Triage and Sending Workflows

    Example session with this skill installed

    Our shared support mailbox has 214 unread messages after the weekend. Build a triage workflow that gives me an action list for Monday morning without losing or mis-marking anything.

    • Read your context and instructions
    • Compiled the email manager

    TRIAGE RUN — produced by applying the skill.

    Setup: Gmail mailbox, app password loaded from a gitignored env file (no credential in code). Folders listed first — resolved threads live under a custom label, recorded by its real name. All references by UID.

    Triage: server-side UNSEEN search returned 214 UIDs. Headers fetched with BODY.PEEK for all 214 — fast, and no message's state changed during triage. Classification against the team's written rules: Act 31 (direct customer questions, 2 flagged URGENT by the subject rule), File 58 (resolved-thread follow-ups, invoices), Notify 44 (weekend monitoring alerts; one contains a renewal deadline, extracted onto the action list), Ignore 81 (newsletters, automated receipts — archived by rule).

    Processing: full bodies fetched only for the 31 Act items and the deadline Notify. Six attachments quarantined; five verified as their claimed types. The sixth claims to be a PDF invoice; magic bytes say executable. Deleted unopened, sender added to the escalate rule.

    State changes: processed messages marked read, nothing else. Unread now means exactly "not yet processed."

    Output: an action list of 33 lines — UID, sender, subject, bucket — the 31 customer questions, the renewal deadline with its date, and the flagged sender. The morning starts from the list, not from scrolling 214 messages.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Email automation usually fails in boring, expensive ways: an auth error that is really the wrong credential type, a triage script that marks everything read and destroys the queue it was meant to organize, an attachment opened on trust. This skill turns mailbox work into a disciplined workflow over IMAP and SMTP that works with Gmail, Outlook, 163, 126, QQ Mail, or a private server. It starts with the connection done right — credentials in environment variables or a gitignored file only, and a provider table covering the app-password and authorization-code rules that cause most authentication failures, plus the port and TLS-mode matching that causes the rest. Then the core method: triage header-first with BODY.PEEK so deciding costs no state change, server-side search instead of downloading everything, UIDs for every reference, and every message classified into exactly one written bucket — Act, File, Notify, or Ignore — with a rule added whenever a message fits none. Bodies and attachments are fetched only for messages that earned it; attachments land in quarantine and are verified by magic bytes, not extensions. Sending gets the same discipline: plain text by default, test-send to yourself before any real recipient, rate spacing, and a send log. A worked example runs a 214-message Monday-morning support inbox down to a 33-line action list, catching a disguised executable on the way. Includes a triage rules template, a send checklist, a workflow health rubric, and a failure table mapping each common symptom to its actual cause.

    • It is a mailbox workflow, not a sending service: bulk, marketing, or high-volume transactional mail belongs on a dedicated platform, and the skill's stop rule says so.
    • Provider quirks shift over time — OAuth requirements in particular keep tightening — so an auth method that works today may need revisiting.
    • It manages one mailbox's state at a time; coordinating several people acting on one shared mailbox needs the bucket-ownership agreement the skill describes, which is an organizational fix, not a technical one.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 24 days ago

    Permissions

    Terminal / Shell
    Network Access
    Listed24 days ago
    Updated21 days ago

    What's inside

    Frequently Asked Questions

    Because for most major providers the login password is the wrong credential. Gmail requires an App Password, 163/126/QQ require an authorization code from webmail settings (with IMAP enabled there first), and Outlook is deprecating basic auth. The skill's provider table maps each service to the credential type it actually accepts — this one table resolves the majority of mailbox automation failures.

    By fetching headers with BODY.PEEK, which reads without setting the seen flag, and by fetching full bodies only for messages the rules promote. Marking happens explicitly, once, after processing — so the unread count always means "not yet processed," and an interrupted run can resume without guessing.

    No — that is the skill's stated stop rule. Mailbox SMTP is for individual and workflow mail at human scale; bulk-shaped sending gets mailboxes throttled or blocked and damages the address's reputation. The skill covers disciplined sending (test-first, rate-spaced, logged) and points bulk work to a proper sending service.

    New in Workflow Automation