email-setup · diff
git:20260411.caef0e4 to git:20260413.d9ff712
16 added, 31 removed. Audit A to A.
---
name: email-setup
- description: Create the assistant's own email address via the Vellum hosted API (one-time setup)
+ description: Register the assistant's own @vellum.me email address (one-time setup)
compatibility: "Designed for Vellum personal assistants"
metadata:
emoji: "📧"
vellum:
display-name: "Email Setup"
feature-flag: "email-channel"
---
- You are setting up your own personal email address. This is a one-time operation - once you have an email, you do not need to run this again.
+ You are setting up your own personal email address. This is a one-time operation — once you have an email, you do not need to run this again.
## Prerequisites
- Only proceed if the user explicitly asks you to create or set up **your own** (the assistant's) email address - e.g., "set up your email", "create your email address", "I want you to have your own email". Generic email requests like "send an email", "check my email", or "set up email" are about the **user's Gmail** and should be handled by the Messaging skill, not this one. Do NOT proactively run this skill.
+ Only proceed if the user explicitly asks you to create or set up **your own** (the assistant's) email address — e.g., "set up your email", "create your email address", "I want you to have your own email". Generic email requests like "send an email", "check my email", or "set up email" are about the **user's personal email** and should be handled by the Messaging skill, not this one. Do NOT proactively run this skill.
## Step 1: Check if Email Already Exists
- Before doing anything, check whether you already have an email address configured:
-
```bash
- assistant email status
+ assistant email status --json
```
- Inspect `health.inboxes` in the response. If at least one inbox exists, tell the user the existing address and stop - do NOT create another one.
-
- ## Step 2: Create Your Email
+ If the command returns an address and status "active", tell the user the existing address and stop — do NOT register another one.
- Create a new inbox through the CLI:
+ ## Step 2: Register Your Email
```bash
- assistant email inbox create --username <your-username>
+ assistant email register <your-username>
```
- For `<your-username>`, use your assistant name (lowercased, alphanumeric only). Check your identity from `IDENTITY.md` or your user persona file (`users/<slug>.md`) to determine your name. If you don't have a name yet, ask the user what username they'd like for your email.
-
- Use the returned `inbox.address` (or `inbox.id` if `address` is empty) as the created email address.
+ For `<your-username>`, use your assistant name (lowercased, alphanumeric only). This creates `<username>@vellum.me`. Check your identity from `IDENTITY.md` to determine your name. If you don't have a name yet, ask the user what username they'd like.
## Step 3: Verify Status
```bash
- assistant email status
+ assistant email status --json
```
- Confirm the created inbox appears in `health.inboxes`.
+ Confirm the address is active.
## Step 4: Confirm Setup
- After the inbox is created and visible in status:
-
1. Tell the user your new email address.
- 2. Store a note in your memory or the user persona file (`users/<slug>.md`) that your email has been provisioned so you remember it in future conversations.
+ 2. Store a note in your memory that your email has been provisioned.
## Rules
- - **One-time only.** If an inbox already exists (Step 1), do not create another. Inform the user of the existing address.
- - **User-initiated only.** Never run this skill unless the user asks you to set up or create an email.
- - **No custom domains.** Use the default provider domain. Do not attempt domain setup.
- - **No API key prompting.** The email API key should already be configured. If the `assistant email` command fails with an API key error, tell the user the email integration is not yet configured and ask them to set it up.
+ - **One-time only.** If an address already exists (Step 1), do not register another.
+ - **User-initiated only.** Never run this skill unless the user asks.
+ - **No API key prompting.** Email is handled through the platform — no provider API keys needed.
## Troubleshooting
- ### API key not configured
-
- If you get an error about a missing API key, the email provider has not been set up. Tell the user:
-
- > "Email isn't configured yet. Please set up the email integration first."
-
- ### Inbox creation failed
+ ### Registration failed
- If inbox creation returns an error (e.g. username taken), try a variation of the name (append a number or use a nickname) and retry once. If it still fails, report the error to the user.
+ If `assistant email register` returns an error (e.g. username taken), try a variation of the name (append a number or use a nickname) and retry once. If it still fails, report the error to the user.