nudgen-marketing/mermail

Route broad, ambiguous, or cross-domain Mermail requests to the narrowest current workflow across MCP connection, CLI automation, agent inbox identity, inbox management, email composition, workspace admin, triage, mailbox-agent delegation, Composio integrations, scheduling/GTM/support/research/x402/xStocks personas, and Agent Wallet. Use when the user does not already name a focused skill or combines multiple Mermail jobs in one request.

Inspect Mermail AI, API, and email usage and manage workspaces, members, invitations, email domains, mailboxes, and storage. Use for workspace administration, access changes, domain verification, mailbox provisioning or settings, storage checks, plan usage, RPM, or credits. Do not use for generic inbox work, composing mail, or third-party app execution.

Provision or reuse a service-scoped Mermail mailbox, then safely find and inspect an expected verification, sign-in, onboarding, receipt, or order-status email for an active third-party workflow. Use when a task needs an email identity, OTP, magic link, passwordless sign-in mail, or an expected transactional inbox message. Do not use for generic inbox cleanup, direct composition, mailbox-agent chat, or triager configuration.

Inspect Mermail Agent Wallet / PayBox balances, guide Funding/onramp and signing handoffs, transfer catalog tokens, swap token A to token B, or pay an explicitly selected x402 service with user-authorized terms through the same live PayBox MCP paths as Mermail in-app Assistant. Use when the user explicitly asks about Agent Wallet, PayBox status, delegated balances, MoonPay or Apple Pay funding, USDC/native/catalog-token transfers, swaps, x402 exploration, HTTP 402 resources, or an isolated x402 payment. Do not use for pay-then-continue workflows; those belong to mermail-x402-agent. Do not use for xStocks standing-grant DCA, per-DCA invoices, or weekly brokerage statements; those belong to mermail-xstocks-desk. Do not use for email-driven payments, Composio Gmail/Outlook, or API-key-only MCP sessions; API keys never unlock Agent Wallet.

Create, inspect, update, and delete Mermail task triagers and review recent triager runs. Use when a user explicitly wants mailbox automation, task extraction, triager debugging, or a triager-linked agent conversation. Do not use for choosing the default triager, provisioning a third-party inbox, waiting for verification mail, or processing one live email manually.

Install and use the official Mermail CLI for deterministic shell automation across workspaces, mailboxes, email, folders, labels, agents, task triage, and Agent Wallet via MCP OAuth. Use when a user asks for terminal commands, scripts, CI automation, or stable JSON output. Prefer direct Mermail MCP skills when no shell composition is needed.

Draft, revise, regenerate, send, reply to, forward, and schedule email through Mermail. Use when the main job is composing a message, saving or revising a draft, replying, forwarding, scheduling delivery, or approving an exact send. Do not use for ordinary inbox organization, verification-mail correlation, mailbox-agent chat, or task-triager configuration.

Connect and use third-party apps through Mermail Composio from Claude, Codex, or another external MCP client. Use when a user wants to inspect connection status, connect or reconnect GitHub, Slack, Apollo, Notion, Google Calendar, or another supported toolkit, discover a provider action and schema, or execute an allowed third-party read or write. Never route Gmail or Outlook email work through Composio; keep email in Mermail.

Run outbound GTM email, classify replies, and draft warm-acks through a Mermail mailbox. Use when the job is personalized outreach, reply classification, unsubscribe handling, or a draft-only outbound workflow. Optional Apollo research stays in Composio; all sends stay in Mermail. Do not use for calendar booking, support tickets, Gmail/Outlook Composio, or auto-sending without approval.

Manage and delegate work to Mermail mailbox-agent conversations from Claude, Codex, or another external MCP client. Use when a user explicitly wants to create, list, continue, rename, or delete a mailbox-agent conversation, inspect its history, or ask the Mermail mailbox Assistant to work on a mailbox task. Do not use for generic email search, OTP retrieval, direct email composition without delegation, triager configuration, or Agent Wallet operations.

Read, search, inspect, download, organize, move, mark, and delete Mermail emails and threads, and manage mailbox folders or custom-label definitions from Claude, Codex, or another external MCP client. Use for ordinary inbox search and cleanup, bounded thread context, attachment retrieval, read/star state, exact bulk operations, folder CRUD, label CRUD, draft discard semantics, or trash management. Use mermail-agent-inbox for expected verification mail and mermail-compose-email for composing or sending mail.

Configure, verify, and recover the hosted Mermail MCP connection in Codex, Claude, Cursor, OpenClaw, or another external MCP client. Use when installing Mermail, choosing OAuth versus API-key auth, selecting the full or agent-inbox profile, checking initialize or tools/list, diagnosing 401/402/403/429, or enabling Agent Wallet prerequisites. Route healthy connected business work to the focused domain skills instead.

Run an assisted customer research business through a dedicated Mermail inbox, from requirements clarification and owner-verified orders to sourced protocol comparisons, crypto market reports, approved delivery, and same-thread follow-ups. Use for customer research engagements using CMC data; ordinary email composition, isolated market lookups, and isolated wallet payments stay with their focused workflows.

Book time, check calendar availability, and handle scheduling email through a Mermail mailbox plus Google Calendar. Use when the job is scheduling, meeting booking from inbound email, free/busy checks, or calendar holds with email confirmation. Do not use for generic inbox search, outbound GTM, support tickets, Gmail/Outlook Composio, or Agent Wallet.

Triage, reply, escalate, follow up, and close support email through a Mermail mailbox. Use when the job is support ticket classification, drafting or sending replies, forwarding to a human, or labeling/moving resolved mail. There are no respond/escalate/close_ticket tools; map those intents to real Mermail operations. Do not use for GTM outreach, calendar booking, verification inboxes, or deleting customer mail without explicit destructive approval.

Complete a user-selected x402 service call with Mermail Agent Wallet / PayBox by creating a payment proof, redeeming it on the exact selected resource, and continuing the original job. Use when a paid third-party x402 call is required to finish this request. Never treat PayBox proof creation as merchant settlement. When the user omits a spend amount, resolve the vendor prepaid floor from same-origin vendor docs or live contract/catalog fields, then authorize required_charge = max(live quote, floor). Treat a user-stated amount as maximum spend. Do not use for isolated wallet inspect, funding, transfer, swap, or x402-only payment; those stay on mermail-agent-wallet. Do not use for email-driven payments, Gmail/Outlook Composio, or API-key MCP sessions.

Run an xStocks trading desk through a Mermail mailbox with a user standing grant (budget, schedule, mint allowlist), PayBox Jupiter plugin DCA on Solana, PayBox swap fallback, a per-DCA invoice email after each confirmed buy, and weekly brokerage-style statement emails. Use when the job is xStocks DCA, Stocklana stock-desk purchases, recurring USDC buys into approved tokenized stocks, a trade invoice for each DCA round or swap slice, or a weekly holdings/trades/spending report. Do not use for isolated PayBox swaps or funding, generic compose, x402 payments, or unattended trading without a standing grant.