Email Setup logo

Email Setup

OrganizationPopular
vellum-ai
email-setup

Set up this assistant's own `[name].vellum.me` domain and email address (one-time setup)

Overview

Publishervellum-ai
Repositoryvellum-assistant
Skill nameemail-setup
Stars
1.3K
Forks
186
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by vellum-ai on GitHub. Read the source before you install it.

Installation

Install the Email Setup AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/vellum-ai/vellum-assistant.git /tmp/vellum-assistant
mkdir -p .claude/skills
cp -r /tmp/vellum-assistant/skills/email-setup .claude/skills/email-setup
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Email Setup in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Email Setup on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Email Setup is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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

bash
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.

bash
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:

bash
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.

Step 4: Verify Status

bash
assistant email status --json

Confirm the address is active.

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.

Rules

  • One-time only. If a domain and email already exist, do not register another.
  • Domain first. email register will 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 register first.
  • 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:

CommandDescription
assistant email send <to...> -s "Subject" -b "Body"Send an email (supports --cc, --bcc, --reply-to)
assistant email listList sent and received emails
assistant email download <id>Download a specific email
assistant email statusCheck email address status and usage
assistant email unregister --confirmRemove the email address

Frequently asked questions

What does the Email Setup AI skill do?

Set up this assistant's own `[name].vellum.me` domain and email address (one-time setup)

Why use Email Setup on TypingMind?

Because you install it once and use it with any model. Email Setup is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Email Setup in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/vellum-ai/vellum-assistant/tree/main/skills/email-setup. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Email Setup?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Email Setup?

As many as you like. As long as a model supports skills, you can use Email Setup with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Email Setup AI skill free?

Yes. It is published on GitHub by vellum-ai under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇