用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt;运行前请先检查来源。
npx skills add https://github.com/vellum-ai/vellum-assistant --skill email-setup命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地?可下载 SkillsMP 当前能够提供的文件。
Use when the user wants to build, scaffold, ship, or edit a Vellum plugin that bundles multiple surfaces (hooks, tools, skills, and more) into one installable package.
Perform a one-time migration from memory v1, to memory v2, which was introduced in 0.8.0.
Migrate from ChatGPT, Claude, OpenClaw, Hermes, Manus, and other AI assistants into Vellum by inspecting their data exports, conversation archives, files, prompts, custom instructions, memory, saved memories, tools, GPTs, workflows, integrations, and relationships, then mapping as much as safely possible into Vellum primitives. Handles single-source and multi-source migrations with a unified, deduplicated inventory.
基于 SOC 职业分类
正在显示 SKILL.md
| name | email-setup |
| description | Set up this assistant's own `[name].vellum.me` domain and email address (one-time setup) |
| compatibility | Designed for Vellum personal assistants |
| metadata | {"emoji":"📧","vellum":{"category":"email","display-name":"Email Setup"}} |
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.
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.
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.
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.
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. mybot@mybot.vellum.me), or ask the user if they prefer a different local part.
assistant email status --json
Confirm the address is active.
email register will fail if no domain is registered. Always check/register the domain before the email.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.
If assistant email register returns an error:
assistant domain register first.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 |