
Extension Email Verification
- 10.6k installs
- Updated August 4, 2026
- caffeinelabs/skills
extension-email-verification is a Caffeine AI Build skill that proves email ownership via click-to-verify links using verifiedEmails.mo and MixinEmailVerification.
About
This Caffeine AI extension skill adds email address verification via a click-to-verify link for plus or pro applications on the Internet Computer. The prefabricated verifiedEmails.mo module maintains a Set of verified addresses; developers check status with contains and must not track verification independently on user profiles. MixinEmailVerification handles inbound verification link callbacks and updates the shared verifiedEmails store. Sending uses sendVerificationEmail from the extension-email dependency, which returns SendResult #ok or #err and delivers per-recipient HTML that must include the {{VERIFICATION_URL}} placeholder. Example Motoko actor code registers users by Principal, enforces email uniqueness via emailToPrincipal, includes the verification mixin, sends a welcome verification email after signup, and exposes isEmailVerified for the caller. Frontend guidance states that any admin UI for verification email content must preserve {{VERIFICATION_URL}} in the body. Use when building signup flows, account recovery gates, or marketing prerequisites that require proof of email ownership inside Caffeine AI backends without custom token plumbing.
- verifiedEmails.mo Set tracks verified addresses; use contains and never duplicate status on user profiles
- MixinEmailVerification handles verification link callbacks and updates the shared verifiedEmails store
- sendVerificationEmail sends per-recipient HTML requiring the {{VERIFICATION_URL}} placeholder
- Example actor registers users, enforces email uniqueness, and exposes isEmailVerified for callers
- Depends on extension-email for outbound mail; plus or pro Caffeine subscription required
Extension Email Verification by the numbers
- 10,626 all-time installs (skills.sh)
- +1,555 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Ranked #85 of 4,347 Backend & APIs skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Aug 5, 2026 (Skillselion catalog sync)
extension-email-verification capabilities & compatibility
Requires Caffeine plus or pro subscription; uses platform email sending via extension-email.
- Capabilities
- email verification links · verified address store · signup verification flow
- Works with
- gmail
- Use cases
- Runs
- Hosted SaaS
- Pricing
- Paid
What extension-email-verification says it does
This skill adds email address verification via a click-to-verify link.
To check whether an email is verified use the `contains` function. Do NOT try to track the email verification status independently by storing it against the user profile.
The htmlBody MUST contain the placeholder text {{VERIFICATION_URL}}
The MixinEmailVerification handles calls to the verification link to verify an email address.
npx skills add https://github.com/caffeinelabs/skills --skill extension-email-verificationAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 10.6k |
|---|---|
| Security audit | 3 / 3 scanners passed |
| Last updated | August 4, 2026 |
| Repository | caffeinelabs/skills ↗ |
How do Caffeine AI apps confirm users own an email address without hand-rolling verification tokens, callbacks, and verified address storage?
Caffeine AI extension for click-to-verify email ownership via Motoko verifiedEmails store and verification link mixin.
Who is it for?
Caffeine AI plus or pro projects needing signup verification, account recovery gates, or prerequisites before marketing or sensitive actions.
Skip if: Marketing broadcasts without extension-email, apps that skip extension-email setup, or teams storing verification flags only on user profiles.
When should I use this skill?
Building Caffeine AI backends that register users, send welcome verification email, handle verification links, or expose isEmailVerified checks.
What you get
Per-recipient verification emails, link-click confirmation, and a prefabricated verifiedEmails Set checked via contains before gating features.
- verification email flow
- verifiedEmails registry
By the numbers
- Skill version 0.1.5
- Two mops dependencies: caffeineai-email-verification ~0.1.1 and caffeineai-email ~0.1.1
Files
Email — Verification
Email verification extension for Caffeine AI.
Overview
This skill adds email address verification via a click-to-verify link. The MixinEmailVerification handles the verification callback; verifiedEmails tracks verified addresses.
Backend
This component is for sending an email to users with a verification link which the user can click to prove they own the email address.
To check if an email address has been verified
Use the prefabricated module mo:caffeineai-email-verification/verifiedEmails.mo which cannot be modified.
```mo:caffeineai-email-verification/verifiedEmails.mo module { public type State = { var verifiedEmails : Set.Set<Text>; };
public func new() : State { { var verifiedEmails = Set.empty<Text>(); }; };
public func contains(state : State, email : Text) : Bool;
public func iter(state : State) : Iter.Iter<Text>;
public func size(state : State) : Nat; };
To check whether an email is verified use the `contains` function. Do NOT try to track the email verification status independently by storing it against the user profile.
### To handle the verification link
Use the prefabricated module `mo:caffeineai-email-verification/verificationMixin.mo` which cannot be modified.
The MixinEmailVerification handles calls to the verification link to verify an email address.
import MixinEmailVerification "mo:caffeineai-email-verification/verificationMixin";
### For sending users a verification email
- This extension depends on the [extension-email](../extension-email/SKILL.md) for sending emails.
- Use the sendVerificationEmail function.
- It returns a SendResult which is #ok if the email is sent successfully otherwise #err(error) with the error text.
- Each recipient receives an individual email with a specific verification link for them
- The htmlBody MUST contain the placeholder text {{VERIFICATION_URL}}
module { public type SendResult = { #ok; #err : Text; };
public func sendVerificationEmail( fromUsername : Text, recipients : [Text], subject : Text, htmlBody : Text, ) : async SendResult; };
### Example usage with endpoints for registering a user and for checking whether a user is verified.
import Map "mo:core/Map"; import Runtime "mo:core/Runtime"; import Principal "mo:core/Principal"; import Text "mo:core/Text"; import EmailClient "mo:caffeineai-email/emailClient"; import MixinEmailVerification "mo:caffeineai-email-verification/verificationMixin"; import VerifiedEmails "mo:caffeineai-email-verification/verifiedEmails";
actor { // Stores which emails are verified let verifiedEmails = VerifiedEmails.new();
// User profiles storage let users = Map.empty<Principal, User>();
// Email to principal mapping for uniqueness check let emailToPrincipal = Map.empty<Text, Principal>();
// Handles the verification link and updates the verifiedEmails store include MixinEmailVerification(verifiedEmails);
type User = { name : Text; email : Text; };
public shared ({ caller }) func registerUser(email : Text, name : Text) : async () { if (users.containsKey(caller)) { Runtime.trap("User already registered"); }; if (emailToPrincipal.containsKey(email)) { Runtime.trap("Email already registered"); };
let user : User = { name; email; }; users.add(caller, user); emailToPrincipal.add(email, caller); let result = await EmailClient.sendVerificationEmail( "no-reply", [email], "Welcome to Our Service", "Hello " # name # ",<br><br>Thank you for registering with our service. Please <a href=\"{{VERIFICATION_URL}}\">click here</a> to verify your email address<br><br>Best regards,<br>The Team", );
switch (result) { case (#ok) {}; case (#err(error)) { Runtime.trap("Couldn't send verification email: " # error); }; }; };
public shared ({ caller }) func isEmailVerified() : async Bool { switch (users.get(caller)) { case (null) { Runtime.trap("User not registered"); }; case (?user) { VerifiedEmails.contains(verifiedEmails, user.email); }; }; }; };
# Frontend
If there is a UI for the admin to enter the content of a verification email then indicate that the placeholder text {{VERIFICATION_URL}} must be present in the email body.
Related skills
FAQ
Where should verified email status be stored?
Use verifiedEmails.mo only; call contains on that module and do not mirror verification state on user profiles.
What placeholder must appear in verification email HTML?
The htmlBody must include {{VERIFICATION_URL}}; each recipient gets an individual link replaced for them.
Which extension is required before using email verification?
This extension depends on extension-email for sendVerificationEmail outbound delivery.
Is Extension Email Verification safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.