Source profileQuality 85/100
vellum-ai/vellum-assistant/skills/email-setup/SKILL.md
email-setup
Set up this assistant's own `[name].vellum.me` domain and email address (one-time setup)
- Source repository stars
- 1,002
- Declared platforms
- 0
- Static risk flags
- 0
- Last source update
- 2026-08-04
- Source checked
- 2026-08-04
Decision brief
What it does—and where it fits
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 emai…
Not for
- Domain registration failed
- Email registration failed
Compatibility matrix
Platform support, with evidence labels
| Platform | Status | Evidence | What to check |
|---|---|---|---|
| Codex | Not declared | No explicit evidence | Portability before use |
| Claude Code | Not declared | No explicit evidence | Portability before use |
| Cursor | Not declared | No explicit evidence | Portability before use |
| Gemini CLI | Not declared | No explicit evidence | Portability before use |
Installation
Inspect first. Install second.
The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.
Source-detected install commandSource
npx skills add https://github.com/vellum-ai/vellum-assistant --skill "skills/email-setup"Safe inspection promptEditorial
Inspect the Agent Skill "email-setup" from https://github.com/vellum-ai/vellum-assistant/blob/32b93fb5c0f5e77d2a15e2f214d3726208c9d208/skills/email-setup/SKILL.md at commit 32b93fb5c0f5e77d2a15e2f214d3726208c9d208. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.
Workflow
What the source asks the agent to do
- 01
Step 1: Check if Domain & Email Already Exist
If both commands show an active domain and email address, tell the user the existing address and stop.
If both commands show an active domain and email address, tell the user the existing address and stop.If an email exists but no domain, the email was set up under the legacy shared domain — it still works. Ask the user if they want to keep it or migrate to a custom subdomain. - 02
Step 2: Register Your Domain
Each assistant gets its own subdomain (e.g. mybot.vellum.me). This must be registered before creating an email address.
Each assistant gets its own subdomain (e.g. mybot.vellum.me). This must be registered before creating an email address.For , use your assistant name (lowercased, alphanumeric, hyphens allowed). Check your identity from IDENTITY.md to determine your name. If you don't have a name yet, ask the user what subdomain they'd like.If the domain is already registered, domain status will show it — skip to Step 3. - 03
Step 3: Register Your Email
Once the domain is active, register your email username on that domain:
Once the domain is active, register your email username on that domain:This creates @.vellum.me. Use the same name as your subdomain for simplicity (e.g. [email protected]), or ask the user if they prefer a different local part. - 04
Step 4: Verify Status
Confirm the address is active.
Confirm the address is active. - 05
Step 5: Confirm Setup
1. Tell the user your new email address. 2. Store a note in your memory that your domain and email have been provisioned.
Tell the user your new email address.Store a note in your memory that your domain and email have been provisioned.1. Tell the user your new email address. 2. Store a note in your memory that your domain and email have been provisioned.
Permission review
Static risk signals and limitations
No configured static risk pattern was detected
This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.
Evidence record
Why each signal appears
EvidenceSourceComputedTestedEditorial
| Signal | Value | Evidence type | Meaning |
|---|---|---|---|
| Quality score | 85/100 | Computed | Documentation, specificity, maintenance, and trust rules |
| Repository stars | 1,002 | Source | Repository attention, not individual Skill quality |
| Compatibility | 0 platforms | Source | Declared in the catalog source record |
| Usage guide | automated source guide | Editorial | Generated or reviewed according to the visible evidence level |
Pinned source
Provenance and original SKILL.md
- Repository
- vellum-ai/vellum-assistant
- Skill path
- skills/email-setup/SKILL.md
- Commit
- 32b93fb5c0f5e77d2a15e2f214d3726208c9d208
- License
- MIT
- Collected
- 2026-08-04
- Default branch
- main
View the original SKILL.md
You are setting up your own custom domain and email address. This is a one-time operation — once you have a domain and 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 personal email and should be handled by the Messaging skill, not this one. Do NOT proactively run this skill.
Step 1: Check if Domain & Email Already Exist
assistant domain status --json
assistant email status --json
If both commands show an active domain and email address, tell the user the existing address and stop.
If an email exists but no domain, the email was set up under the legacy shared domain — it still works. Ask the user if they want to keep it or migrate to a custom subdomain.
Step 2: Register Your Domain
Each assistant gets its own subdomain (e.g. mybot.vellum.me). This must be registered before creating an email address.
assistant domain register <subdomain>
For <subdomain>, use your assistant name (lowercased, alphanumeric, hyphens allowed). Check your identity from IDENTITY.md to determine your name. If you don't have a name yet, ask the user what subdomain they'd like.
If the domain is already registered, domain status will show it — skip to Step 3.
Step 3: Register Your Email
Once the domain is active, register your email username on that domain:
assistant email register <username>
This creates <username>@<subdomain>.vellum.me. Use the same name as your subdomain for simplicity (e.g. [email protected]), or ask the user if they prefer a different local part.
Step 4: Verify Status
assistant email status --json
Confirm the address is active.
Step 5: Confirm Setup
- Tell the user your new email address.
- Store a note in your memory that your domain and email have been provisioned.
Rules
- One-time only. If a domain and email already exist, do not register another.
- Domain first.
email registerwill fail if no domain is registered. Always check/register the domain before the email. - User-initiated only. Never run this skill unless the user asks.
- No API key prompting. Email is handled through the Vellum platform — no provider API keys or DNS configuration needed.
Troubleshooting
Domain registration failed
If assistant domain register returns an error (e.g. subdomain taken), try a variation (append a number or use a nickname) and retry once. If it still fails, report the error to the user.
Email registration failed
If assistant email register returns an error:
- "No domain registered" — run
assistant domain registerfirst. - Username taken — try a different local part.
- Other errors — report the error to the user.
Email Management
Once set up, the assistant has full email capabilities:
| Command | Description |
|---|---|
assistant email send <to...> -s "Subject" -b "Body" | Send an email (supports --cc, --bcc, --reply-to) |
assistant email list | List sent and received emails |
assistant email download <id> | Download a specific email |
assistant email status | Check email address status and usage |
assistant email unregister --confirm | Remove the email address |