Email logo

Email

Community
whawkinsiv
email

Use this skill to set up a professional email address on the founder's domain and make sure email lands in inboxes: 'hello@ email,' 'branded email,' 'business email,' 'email forwarding,' 'send from my domain,' 'SPF,' 'DKIM,' 'DMARC,' 'my emails go to spam,' or 'set up email for my app.' Covers a free forwarding setup, sending as the branded address, the three DNS records, and app email from a subdomain. Not for onboarding or win-back email sequences (use retention) or for writing outreach (use first-customers).

Overview

Publisherwhawkinsiv
Repositorysolo-founder-skills
Skill nameemail
Stars
260
Forks
44
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 whawkinsiv on GitHub. Read the source before you install it.

Installation

Install the Email 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.
    https://github.com/whawkinsiv/solo-founder-skills/tree/main/skills/email
  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/whawkinsiv/solo-founder-skills.git /tmp/solo-founder-skills
mkdir -p .claude/skills
cp -r /tmp/solo-founder-skills/skills/email .claude/skills/email
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Email 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 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 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.

Email

Set up hello@yourdomain.com before the first outreach. A message from a personal webmail address reads as a side project. One that lands in spam is never read.

Step 1: Receive mail at the domain

Forward hello@ to the founder's existing inbox. Many DNS providers and registrars offer free forwarding (for example, Cloudflare Email Routing). Add aliases for support@ and billing@ that forward to the same inbox, and filter them by label.

Step 2: Send as the branded address

Pick one option:

  • Free: add the address in the inbox's "send mail as" setting, through the SMTP relay of a transactional email service. Verify the domain in that service first.
  • Paid and simpler: a hosted mailbox on the domain (Google Workspace, Fastmail, or similar). Choose this when the founder wants less setup, needs calendar invites from the branded address, or adds a second person.

Make the branded address the default "from" address.

Step 3: Add SPF, DKIM, and DMARC

These DNS records prove the mail is really from the domain. Without them, mail lands in spam and anyone can send mail that pretends to be the founder.

  • SPF: one TXT record that lists every service allowed to send for the domain. A domain may have only one SPF record. Merge the include: entries into it.
  • DKIM: each sending service gives you its own record. Add every one.
  • DMARC: start with monitoring only:
    _dmarc  TXT  v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com
    After 2–4 weeks of reports that show only your own services sending, change p=none to p=quarantine. A strict policy set up too early can send the founder's own mail to spam.

Verify: send a message to a Gmail address, open "Show original", and check that SPF, DKIM, and DMARC all show PASS.

Step 4: App email

  • Send password resets, receipts, and notifications through a transactional email service, from a subdomain such as mail.yourdomain.com. That keeps problems with app email from hurting the main domain's reputation.
  • Use a real reply-to address, not noreply@. Customer replies are the cheapest feedback there is.
  • Include a plain-text version of every message.
  • Marketing email needs a one-click unsubscribe link. Never send bulk marketing from the founder's personal inbox setup.

Rules

  • Keep cold outreach small: 10–20 personal messages a day from the main domain. Bulk cold email ruins a domain's reputation.
  • Set up the records before the first send, not after mail starts landing in spam.

Output

A working hello@ address that sends and receives, the DNS records added, and a test message with SPF, DKIM, and DMARC all at PASS.

Frequently asked questions

What does the Email AI skill do?

Use this skill to set up a professional email address on the founder's domain and make sure email lands in inboxes: 'hello@ email,' 'branded email,' 'business email,' 'email forwarding,' 'send from my domain,' 'SPF,' 'DKIM,' 'DMARC,' 'my emails go to spam,' or 'set up email for my app.' Covers a free forwarding setup, sending as the branded address, the three DNS records, and app email from a subdomain. Not for onboarding or win-back email sequences (use retention) or for writing outreach (use first-customers).

Why use Email on TypingMind?

Because you install it once and use it with any model. Email 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 in TypingMind?

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

Which AI models can use Email?

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?

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

Is the Email AI skill free?

Yes. It is published on GitHub by whawkinsiv 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 👇