Menu
Guide the user through setting up email sending domains, configuring EMAIL_RESPOND_TO, and understanding email capabilities.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Use this skill to setup your knowledge base, improve your setup, edit /support/summary, change tone of voice, setup daily reporting, setup human escalation.
Guide the user through creating a sales pipeline — name, stages with probabilities, deal creation rules, and deal movement automations.
Guide the user through setting up a stall deal recovery policy — timing thresholds, per-stage actions, and an automated schedule. Use when the user asks about inactive deals, follow-up automation, or stale leads.
Execute a stall deal check — query stalled deals, send follow-ups per stage policy, archive long-inactive deals as Lost.
Guide the user through setting up a welcome email template and automation for new contacts.
Read scenario scores and trajectories in scenario-dumps/, diagnose patterns across models, understand root causes, propose and apply changes to skill/prompt files.
| name | resend-email-setup |
| description | Guide the user through setting up email sending domains, configuring EMAIL_RESPOND_TO, and understanding email capabilities. |
Use email_setup_domain(op="help") to see all available operations.
Strongly recommend a subdomain (e.g. mail.example.com) instead of the main domain, especially for inbound emails.
Steps:
email_setup_domain(op="add", args={"domain": "...", "region": "...", "enable_receiving": true/false})email_setup_domain(op="verify", args={"domain_id": "..."})If no domain is configured yet, the user can send from the testing domain — call email_setup_domain(op="help") to see it.
Never use flexus_my_setup() for email domains — they are saved automatically via the email_setup_domain() tool.
If the user wants to use their own Resend account, they should connect it via the Integrations page — the webhook is created automatically on connect.
Users can configure EMAIL_RESPOND_TO addresses in bot setup. Emails to those addresses become tasks the bot handles. All other inbound emails are logged as CRM activities only.
Allowed: transactional, replies, welcome emails, follow-ups to contacts who had a conversation or requested info. Forbidden: cold outreach, mass campaigns to contacts who never interacted, bulk promo without opt-in.