PluginBench
Skill
Pass
Audit score 90

extension-email-verification

caffeinelabs/skills

Send click-to-verify email links to confirm user email ownership.

What is extension-email-verification?

This skill adds email verification functionality by sending users a unique verification link they can click to prove they own their email address. Use it when you need to validate email addresses during user registration or account changes.

  • Send verification emails with unique click-to-verify links to recipients
  • Track verified email addresses using the built-in verifiedEmails module
  • Handle verification callbacks automatically via MixinEmailVerification
  • Check if an email has been verified using the contains function
  • Support multiple recipients with individual verification links per email

How to install extension-email-verification

npx skills add https://github.com/caffeinelabs/skills --skill extension-email-verification
Prerequisites
  • Caffeine AI Plus or Pro subscription
  • extension-email skill installed (dependency)
  • caffeineai-email-verification ~0.1.1 and caffeineai-email ~0.1.1 packages
Claude Code
Cursor
Windsurf
Cline

How to use extension-email-verification

  1. 1.Import the VerifiedEmails and MixinEmailVerification modules into your backend
  2. 2.Initialize verifiedEmails state using VerifiedEmails.new()
  3. 3.Include MixinEmailVerification in your actor to handle verification callbacks
  4. 4.Create an endpoint to send verification emails using EmailClient.sendVerificationEmail()
  5. 5.Include the {{VERIFICATION_URL}} placeholder in your email HTML body
  6. 6.Use VerifiedEmails.contains() to check if an email is verified before granting access

Use cases

Good for
  • User registration workflows requiring email confirmation
  • Account email change verification
  • Two-factor authentication via email link
  • Preventing duplicate email registrations
  • Validating contact information before sending sensitive communications
Who it's for
  • Backend developers building user registration systems
  • Teams implementing email-based account verification
  • Applications requiring email ownership validation
  • Caffeine AI users on Plus or Pro subscription tiers

extension-email-verification FAQ

What happens when a user clicks the verification link?

The MixinEmailVerification mixin automatically handles the callback and updates the verifiedEmails store to mark that email as verified.

Can I customize the verification email content?

Yes, you control the subject and HTML body of the email. You must include the {{VERIFICATION_URL}} placeholder where the verification link should appear.

How do I check if a user's email is verified?

Use the VerifiedEmails.contains(verifiedEmails, email) function to check if an email address is in the verified set.

Can multiple users register with the same email?

The skill doesn't prevent this automatically. You should implement your own uniqueness check before allowing registration, as shown in the example.

What subscription level is required?

This skill requires a Caffeine AI Plus or Pro subscription.

Full instructions (SKILL.md)

Source of truth, from caffeinelabs/skills.


name: extension-email-verification description: Support for sending an email with a link the recipient can click to prove they own the email address. version: 0.1.5 compatibility: mops: caffeineai-email-verification: "~0.1.1" caffeineai-email: "~0.1.1" caffeineai-subscription: [plus, pro]

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.

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