email-setup

Register an assistant subdomain and provision a dedicated email address.

2|2|Updated May 13, 2026
One-click install
npx skills add https://github.com/autonomy-cloud/kairos-interface --skill email-setup-autonomy-cloud
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: email-setup
Source: https://github.com/autonomy-cloud/kairos-interface/tree/main/skills/email-setup
Command: npx skills add https://github.com/autonomy-cloud/kairos-interface --skill email-setup-autonomy-cloud

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provisions a dedicated email address for the assistant itself on a custom subdomain, avoiding repeated setup and ensuring the assistant can send and receive messages under its own identity.

Core Features & Use Cases

  • One-time assistant domain registration: Checks whether a domain and email already exist, registers the assistant subdomain if needed, then provisions the email on the active domain.
  • Clear separation from user email workflows: Only runs when the user explicitly requests setup of the assistant’s own email, not the user’s personal email.
  • Status verification and safe stopping: Uses domain and email status checks to avoid duplicate registrations and confirms the result after provisioning.

Quick Start

Tell me: set up your email address for my assistant (email-setup) using your assistant subdomain.

Frequently Asked Questions about email-setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I provision a dedicated email address for my assistant on a custom subdomain?

To provision a dedicated assistant email address, the system performs idempotent checks on domain and email status, registers the assistant subdomain, provisions the email after domain activation, and verifies the result via email status.

What is the domain-first registration process for setting up an assistant email identity?

Domain-first registration requires checking domain status, registering the assistant subdomain first, waiting for domain activation, and then provisioning the email address to ensure a valid fully qualified identity.

Can I use this email setup process for my personal user email workflows?

No, this email setup process only runs when explicitly provisioning the assistant's own email identity, providing clear separation from user email workflows and personal email configurations.

What happens if I try to register an assistant email that already exists?

If an assistant email already exists, the idempotent checks via domain status and email status prevent duplicate registrations, allowing the process to safely stop and confirm the existing provisioning result.

Do I need to manually verify my assistant email after domain provisioning?

No manual verification is needed because the setup includes a final verification step using email status to automatically confirm the assistant email was successfully provisioned on the active domain.

When should I use custom subdomain email provisioning instead of legacy shared domains?

Use custom subdomain email provisioning during Vellum personal assistant onboarding when the assistant needs its own fully qualified name.vellum.me email identity instead of relying on legacy shared domains.