What problem does it solve? Setting up product email (notifications, receipts, verification codes, digests) on Weegloo requires choosing an SMTP vendor, registering an EmailAccount with correct credentials, and wiring a Script's EmailSend — with vendor-specific pitfalls that silently fail. This Skill guides the full flow, defaulting to Gmail SMTP when no vendor is named. ## Core Features & Use Cases - Vendor selection with a Google default: When the user names no SMTP service, it uses Gmail (smtp.gmail.com:587/StartTls) and asks only for a Google App Password and its account address; it also covers Naver, Resend, and Brevo presets with per-vendor username/password/fromAddress rules. - EmailAccount creation guidance: Explains that creating an account sends a real test message before persisting, that endpoint/username/password are immutable (rotation means recreate), and that Update is REST-only, not an MCP tool. - Permission and plan constraints: Details the SETTING_EMAIL_ACCOUNT permission, token-type restrictions (no SpaceAccessToken), and plan limits on custom SMTP hosts. - Use Case: A user building a booking product needs order confirmation emails; the Skill walks them through creating a Gmail App Password, registering the EmailAccount, and pointing a Script's EmailSend at it. ## Quick Start Set up email sending for my Weegloo space so my app can send order confirmation emails.