@rubytech/taskmaster 1.11.0 → 1.11.1

package/dist/build-info.json

@@ -1,5 +1,5 @@
 {
-  "version": "1.11.0",
-  "commit": "24430be4b288d224c6be04aa31910f9cbb2adc1d",
-  "builtAt": "2026-03-01T11:29:23.837Z"
+  "version": "1.11.1",
+  "commit": "8d046d383d7f5333a6b81d355d6d5b36f470f9ce",
+  "builtAt": "2026-03-01T13:29:28.295Z"
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rubytech/taskmaster",
-  "version": "1.11.0",
+  "version": "1.11.1",
   "description": "AI-powered business assistant for small businesses",
   "publishConfig": {
     "access": "public"

package/skills/brevo/references/browser-setup.md

@@ -2,11 +2,14 @@
 
 Walk the user through getting Brevo credentials. Brevo uses single sender verification — the user verifies an email address by entering a 6-digit code sent to it. No DNS records required. Guide with clear instructions.
 
+**Important:** Brevo is primarily a marketing email platform. The signup flow and dashboard are oriented around marketing campaigns, contacts, and newsletters. The user does NOT need any of that. Guide them directly to the two things they need: a verified sender and an API key. Both are in the **Settings** page — accessed via the **gear icon** in the top-right toolbar. On the Settings page, both options are in the left sidebar under **Organization settings**.
+
 ---
 
 ## Prerequisites
 
 - User has an email address they want OTP emails to come from (e.g. their business email)
+- User has a mobile phone number (required by Brevo for account activation)
 - Chat channel for sending instructions
 
 ---
@@ -21,50 +24,80 @@ Tell the user what Brevo is and why they need it:
 
 ## Step 2: Create a Brevo account
 
-> "Go to **brevo.com** in your browser and click **Sign up free**.
+> "Go to **brevo.com** in your browser and click **Sign Up Free** in the top-right corner.
 >
 > You'll need to enter:
-> - Your email address
-> - A password
+> - Your **email address**
+> - A **password**
+>
+> You can also sign up with Google or Apple if that's easier.
+>
+> After clicking **Create an account**, Brevo will send a confirmation email. Click the link in it to verify your account.
 >
-> Brevo will send a confirmation email. Click the link in it to verify your account. Let me know when you're logged in."
+> **Next, Brevo will ask for your mobile phone number.** This is for account activation only — they send a text to verify you're a real person. Enter your number and the code they text you.
+>
+> Let me know when you're past that and logged in."
+
+Wait for the user to confirm they've completed signup and mobile verification.
 
-Wait for the user to confirm they've completed signup.
+### Getting past the onboarding
 
-If the user is asked onboarding questions (company name, team size, etc.), tell them:
+After signup, Brevo lands on a **"Getting Started"** page that tries to walk you through creating contacts, campaigns, and other marketing features. The user does NOT need any of this.
 
-> "Just fill in your business name and pick whatever options feel right — those are for Brevo's records and don't affect anything."
+If the user mentions being on a "Getting Started" page, or asks about contacts/campaigns/templates:
+
+> "You can skip all of that — it's for email marketing campaigns, which we don't need. We just need two things from Brevo: a verified sender address and an API key. Both are in the account settings. Let me show you where."
+
+If the user is asked onboarding questions (company name, team size, etc.):
+
+> "Just fill in your business name and pick whatever options feel right — those are for Brevo's records and don't affect anything we're doing."
 
 ## Step 3: Verify a sender email address
 
 This determines what email address OTP codes come from. Brevo sends a 6-digit code to the email — no DNS records needed.
 
+**Navigation: Settings page (gear icon) → Organization settings → Senders, domains, IPs.**
+
 > "Now we need to verify the email address that verification codes will be sent from. This is what your visitors will see in their inbox.
 >
-> 1. In the Brevo dashboard, click your **name/icon** in the top-right
-> 2. Click **Senders, Domains & Dedicated IPs** (or go to **Settings → Senders**)
-> 3. Click **Add a sender**
+> 1. In the **top-right toolbar**, click the **gear icon** (⚙️) to open **Settings**
+> 2. In the Settings left sidebar, under **Organization settings**, click **Senders, domains, IPs**
+> 3. Click the **Add sender** button (top-right of the page)
 > 4. Fill in:
 >    - **From Name** — your business name (e.g. "Acme Plumbing")
 >    - **From Email** — the email you want codes to come from (your business email works)
-> 5. Click **Save**
+> 5. Click **Add sender**
+> 6. A popup will appear saying **"Authenticate your domain now?"** — you have two options:
+>    - **"Do it later"** — skip domain authentication. Sender verification alone is enough to send verification codes. Choose this if you don't own the email domain or want the simplest setup.
+>    - **"Authenticate domain"** — lets Brevo's partner (Entri) automatically add DKIM and DMARC records to your domain. This improves email deliverability and makes your emails fully compliant with Gmail/Yahoo/Microsoft requirements. Choose this if you own the domain and want more robust delivery. Entri will ask you to log in to your domain provider and it handles the DNS records automatically — no technical knowledge needed.
 >
-> Brevo will send a **6-digit code** to that email address. Check your inbox (and spam folder), enter the code, and click **Verify**. Let me know when it's done."
+> Either way, Brevo will send a **6-digit code** to your email address. Check your inbox (and spam folder), enter the code, and click **Verify**. Let me know when it's done."
+
+If the user says they can't find it:
+
+> "In the top-right of the Brevo dashboard, there's a toolbar with several small icons. Click the **gear icon** (⚙️) — it should be between the help icon and the notification bell. That opens the Settings page. Then look in the left sidebar for **Senders, domains, IPs** under the **Organization settings** section."
+
+**Do NOT direct users to "Transactional" in the main dashboard sidebar or to "Campaigns".** Those are marketing features, not what they need.
 
 Wait for the user to confirm.
 
 ## Step 4: Get an API key
 
+**Navigation: same Settings page → Organization settings → SMTP & API.**
+
 > "Almost done. Now we need an API key:
 >
-> 1. Click your **name/icon** in the top-right again
-> 2. Click **SMTP & API**
-> 3. Click the **API Keys** tab
-> 4. Click **Generate a new API key**
-> 5. Give it a name like **Taskmaster**
-> 6. Click **Generate**
+> 1. You should still be on the Settings page. In the left sidebar under **Organization settings**, click **SMTP & API**
+> 2. Click the **API keys & MCP** tab (not the SMTP tab)
+> 3. Click **Generate a new API key**
+> 4. Give it a name like **Taskmaster**
+> 5. Click **Generate**
 >
-> You'll see the API key — it starts with **xkeysib-** and is quite long. **Copy it now**. Send it to me."
+> You'll see the API key — it starts with **xkeysib-** and is quite long. **Copy it now** — Brevo only shows it once. If you lose it, you'll need to generate a new one. Send me the key."
+
+If the user navigated away from Settings:
+
+> "Click the **gear icon** (⚙️) in the top-right toolbar to get back to Settings, then click **SMTP & API** in the left sidebar."
 
 Wait for the user to send the API key.
 
@@ -96,7 +129,20 @@ Check if they have a verified sender:
 
 If yes, skip to Step 4. If they're unsure:
 
-> "Go to **Settings → Senders** in Brevo and check if there's a verified sender listed. If not, we'll set one up."
+> "Click the **gear icon** (⚙️) in the top-right toolbar to open Settings. Then click **Senders, domains, IPs** in the left sidebar. Check if there's a verified sender listed. If not, we'll set one up."
+
+---
+
+## Troubleshooting
+
+| Problem | Solution |
+|---------|----------|
+| Can't find Senders or SMTP & API | Click the **gear icon** (⚙️) in the top-right toolbar to open the Settings page. Both options are in the left sidebar under **Organization settings**. |
+| Landed on "Getting Started" or campaign builder | Ignore it — click the **gear icon** (⚙️) in the top-right toolbar to go straight to Settings. |
+| "Transactional" page shows SMTP settings | Wrong place — that's in the main dashboard, not Settings. Click the **gear icon** (⚙️) in the top-right toolbar, then **SMTP & API** in the Settings sidebar. |
+| Clicked "Authenticate domain" by mistake | If you end up on a Domains page or see DNS/Entri prompts, click **Cancel** or close the modal, then click the **Senders** tab to get back to sender verification. |
+| Mobile verification code not arriving | Wait a minute and try again. Check you entered the right country code. Some VoIP numbers don't work — use a real mobile number. |
+| Can't find the free plan | On brevo.com/pricing, the free tier is the green banner at the top of the page ("Free forever, no credit card needed"). Click **Sign up free** there. |
 
 ---
 
@@ -105,9 +151,11 @@ If yes, skip to Step 4. If they're unsure:
 | Question | Answer |
 |----------|--------|
 | "Is it free?" | Yes — 300 emails per day, forever. No credit card required. For verification codes, that's more than enough. |
+| "Why do they need my phone number?" | Brevo requires a mobile number for account activation — it's a one-time verification to prevent spam accounts. They won't call or text you after that. |
 | "Can I use my Gmail/Outlook address?" | Yes, as long as you verify it by entering the 6-digit code Brevo sends to it. |
 | "Will emails go to spam?" | OTP emails are solicited (the user just clicked 'send me a code'), so they almost always reach the inbox. If a visitor doesn't see it, tell them to check spam. |
-| "I lost my API key" | Go to SMTP & API → API Keys in Brevo and generate a new one. |
+| "I lost my API key" | Click the gear icon (⚙️) in the top-right toolbar → SMTP & API → API keys & MCP tab, and generate a new one. |
 | "Do I need to set up DNS records?" | No. Single sender verification works without DNS. Brevo will recommend domain authentication for better deliverability, but it's not required. |
 | "Can I change the sender address later?" | Yes — add and verify a new sender in Brevo. Taskmaster auto-detects the verified sender, so no changes needed on this end. |
 | "Where does Taskmaster get the sender address?" | Automatically from the Brevo API. When you verify a sender in Brevo, Taskmaster detects it — you don't need to enter it anywhere else. |
+| "What about all the marketing stuff?" | Ignore it. Brevo is a full marketing platform, but we only use its transactional email API. You don't need to set up contacts, campaigns, or templates. |

package/taskmaster-docs/USER-GUIDE.md

@@ -1472,10 +1472,10 @@ By default, anyone who opens the public chat can start a conversation immediatel
 | Method | How it works | What you need |
 |--------|-------------|---------------|
 | **Anonymous** | No verification — visitors chat immediately | Nothing (default) |
-| **Email OTP** | Visitors enter their email, receive a one-time code | A [SendGrid](https://sendgrid.com) API key and a verified sender (free tier available). The sender address is configured in SendGrid, not in Taskmaster. |
+| **Email OTP** | Visitors enter their email, receive a one-time code | A [Brevo](https://brevo.com) API key and a verified sender (free, no credit card). The sender address is configured in Brevo, not in Taskmaster. |
 | **SMS OTP** | Visitors enter their phone number, receive a one-time code | [Twilio](https://twilio.com) account SID, auth token, and a Twilio phone number |
 
-5. Enter your provider credentials — for email, add the SendGrid API key in the **API Keys** section on the Setup page; for SMS, enter Twilio credentials in the SMS Fallback fields
+5. Enter your provider credentials — for email, add the Brevo API key in the **API Keys** section on the Setup page; for SMS, enter Twilio credentials in the SMS Fallback fields
 6. Settings auto-save when you leave each field
 
 Once enabled, visitors must authenticate before they can send their first message. Verified contact details are stored and available to the agent via the `verify_contact` tool, so your assistant knows who it's talking to.