Token导航 LogoToken导航

Agent Skill · 开发

didit-email-verification(迪迪特电子邮件验证)

didit-email-verification 用于补充开发相关能力,适合在 OpenClaw 中需要让 Agent 承接开发相关任务时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

didit-email-verification 是开发类 Agent Skill,可用宿主为 OpenClaw,通过ClawHub获取,权限为接触敏感数据;许可证为 MIT-0,第三方扫描已通过,按安装量在开发类的 21,746 个 Skill 里排第 3,483。

总安装 11,215周安装 472GitHub Stars 公开资料未说明下载 3,927核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT-0
版本
1.2.0

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:didit-email-verification(迪迪特电子邮件验证)
来源仓库:https://github.com/rosasalberto/didit-email-verification
安装命令:
openclaw skills install didit-email-verification
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install didit-email-verification

这个 Skill 是做什么的

开发类 Skill 面向写代码、改代码和排查问题,一般会读写仓库文件,部分还会执行构建或测试命令。

通过一次性密码 (OTP) 方式验证电子邮件地址有效性的独立 API。适用于用户注册、密码找回或营销邮件发送前的地址清洗流程。发送验证码至邮箱,用户输入后返回真伪判定结果。didit-email-verification 属于开发类 Skill,可作为该场景下的辅助能力补充。

支持 SMTP 与 HTTP 双通道投递,送达率受收件箱策略影响。请勿滥用发送接口,否则可能导致 IP 被标记为垃圾邮件源。

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 OpenClaw;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 openclaw skills install didit-email-verification;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要接触敏感数据,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

didit-email-verification 怎么安装?

在终端执行 openclaw skills install didit-email-verification。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

didit-email-verification 支持哪些 AI 工具?

公开资料标注支持 OpenClaw。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

didit-email-verification 需要什么权限?

权限级别是接触敏感数据。该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

didit-email-verification 是免费的吗?

来源标注的许可证是 MIT-0。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

didit-email-verification 用的人多吗?

公开数据是累计安装 11,215 次,近一周安装 472 次,下载 3,927 次。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

didit-email-verification 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 专注 OpenClaw 一种宿主,触发方式和使用习惯不用来回切换。
  • 许可证明确为 MIT-0,商用和分发边界好判断。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 需要接触敏感数据,装到常用环境前要先评估影响面。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 OpenClaw,想直接扩展它能力的人。
  • 需要处理开发类任务、又不想每次都手写提示词的人。
  • 需要许可证清楚、并且有第三方扫描结果的团队项目。

不太适合

  • 环境里有大量密钥、凭证,不方便给第三方 Skill 读取的人。
  • 需要厂商级技术支持和 SLA 的生产系统。

开发类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
skill-vetter

技能审查员 · OpenClaw

8,779,018986操作浏览器MIT-0通过
ontology

本体论 · OpenClaw

6,636,960576只读MIT-0通过
entra-app-registration

内部应用程序注册 · Codex、Claude

6,631,872764接触敏感数据未明确通过
entra-app-registration

内部应用程序注册 · Codex、Claude

3,757,680201接触敏感数据未明确通过
nano-banana-pro

纳米香蕉专业版 · OpenClaw

3,526,898364接触敏感数据MIT-0有提醒
didit-email-verification

迪迪特电子邮件验证 · 本页

11,215—接触敏感数据MIT-0通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

name
didit-email-verification
description
>
version
1.2.0
metadata
openclaw
requires
env
primaryEnv
DIDIT_API_KEY
emoji
✉️
homepage
https://docs.didit.me

Didit Email Verification API

Overview

Two-step email verification via one-time code:

  1. Send a verification code to an email address
  2. Check the code the user provides

Key constraints:

  • Code expires after 5 minutes
  • Maximum 3 verification attempts per code (then must resend)
  • Maximum 2 resend requests within 24 hours
  • You must call Send before Check — Check returns "Expired or Not Found" otherwise

Capabilities: Detects breached emails (via known data breaches), disposable/temporary email providers, and undeliverable addresses. Supports fraud signals for risk scoring.

API Reference: Send Code | Check Code Feature Guide: https://docs.didit.me/core-technology/email-verification/overview


Authentication

All requests require an API key via the x-api-key header.

How to obtain: Didit Business Console → API & Webhooks → Copy API key, or via programmatic registration (see below).

x-api-key: your_api_key_here
401 = API key missing or invalid. 403 = key lacks permissions or insufficient credits.

Getting Started (No Account Yet?)

If you don't have a Didit API key, create one in 2 API calls:

  1. Register: POST https://apx.didit.me/auth/v2/programmatic/register/ with {"email": "you@gmail.com", "password": "MyStr0ng!Pass"}
  2. Check email for a 6-character OTP code
  3. Verify: POST https://apx.didit.me/auth/v2/programmatic/verify-email/ with {"email": "you@gmail.com", "code": "A3K9F2"} → response includes api_key

To add credits: GET /v3/billing/balance/ to check, POST /v3/billing/top-up/ with {"amount_in_dollars": 50} for a Stripe checkout link.

See the didit-verification-management skill for full platform management (workflows, sessions, users, billing).


Step 1: Send Email Code

Sends a one-time verification code to the specified email address.

Request

POST https://verification.didit.me/v3/email/send/

Headers

HeaderValueRequired
x-api-keyYour API keyYes
Content-Typeapplication/jsonYes

Body (JSON)

ParameterTypeRequiredDefaultConstraintsDescription
emailstringYes—Valid emailEmail address to send code to
options.code_sizeintegerNo6Min: 4, Max: 8Length of the verification code
options.alphanumeric_codebooleanNofalse—true = A-Z + 0-9 (case-insensitive)
options.localestringNo—Max 5 charsLocale for email template. e.g. en-US
signals.ipstringNo—IPv4 or IPv6User's IP for fraud detection
signals.device_idstringNo—Max 255 charsUnique device identifier
signals.user_agentstringNo—Max 512 charsBrowser/client user agent
vendor_datastringNo——Your identifier for session tracking

Example

import requests

response = requests.post(
    "https://verification.didit.me/v3/email/send/",
    headers={"x-api-key": "YOUR_API_KEY", "Content-Type": "application/json"},
    json={
        "email": "user@example.com",
        "options": {"code_size": 6},
        "signals": {"ip": "203.0.113.42"},
        "vendor_data": "session-abc-123",
    },
)
print(response.status_code, response.json())
const response = await fetch("https://verification.didit.me/v3/email/send/", {
  method: "POST",
  headers: { "x-api-key": "YOUR_API_KEY", "Content-Type": "application/json" },
  body: JSON.stringify({
    email: "user@example.com",
    options: { code_size: 6 },
    signals: { ip: "203.0.113.42" },
  }),
});

Response (200 OK)

{
  "request_id": "e39cb057-92fc-4b59-b84e-02fec29a0f24",
  "status": "Success",
  "reason": null
}

Status Values & Handling

StatusMeaningAction
"Success"Code sentProceed — wait for user to provide code, then call Check
"Retry"Temporary delivery issueWait a few seconds and retry Send (max 2 retries)
"Undeliverable"Email cannot receive mailInform user the email is invalid or cannot receive messages

Error Responses

CodeMeaningAction
400Invalid request body or emailCheck email format and parameter constraints
401Invalid or missing API keyVerify x-api-key header
403Insufficient credits/permissionsCheck credits in Business Console
429Rate limitedBack off and retry after indicated period

Step 2: Check Email Code

Verifies the code the user received. Must be called after a successful Send. Optionally auto-declines risky emails.

Request

POST https://verification.didit.me/v3/email/check/

Headers

HeaderValueRequired
x-api-keyYour API keyYes
Content-Typeapplication/jsonYes

Body (JSON)

ParameterTypeRequiredDefaultValuesDescription
emailstringYes—Valid emailSame email used in Step 1
codestringYes—4-8 charsThe code the user received
duplicated_email_actionstringNo"NO_ACTION""NO_ACTION" / "DECLINE"Decline if email already verified by another user
breached_email_actionstringNo"NO_ACTION""NO_ACTION" / "DECLINE"Decline if email found in data breaches
disposable_email_actionstringNo"NO_ACTION""NO_ACTION" / "DECLINE"Decline if email is disposable/temporary
undeliverable_email_actionstringNo"NO_ACTION""NO_ACTION" / "DECLINE"Decline if email is undeliverable
Policy note: When an action is "DECLINE", verification is rejected even if the code is correct. The email.* fields are still populated so you can inspect why.

Example

response = requests.post(
    "https://verification.didit.me/v3/email/check/",
    headers={"x-api-key": "YOUR_API_KEY", "Content-Type": "application/json"},
    json={
        "email": "user@example.com",
        "code": "123456",
        "breached_email_action": "DECLINE",
        "disposable_email_action": "DECLINE",
    },
)
const response = await fetch("https://verification.didit.me/v3/email/check/", {
  method: "POST",
  headers: { "x-api-key": "YOUR_API_KEY", "Content-Type": "application/json" },
  body: JSON.stringify({
    email: "user@example.com",
    code: "123456",
    breached_email_action: "DECLINE",
    disposable_email_action: "DECLINE",
  }),
});

Response (200 OK)

{
  "request_id": "e39cb057-92fc-4b59-b84e-02fec29a0f24",
  "status": "Approved",
  "message": "The verification code is correct.",
  "email": {
    "status": "Approved",
    "email": "user@example.com",
    "is_breached": false,
    "breaches": [],
    "is_disposable": false,
    "is_undeliverable": false,
    "verification_attempts": 1,
    "verified_at": "2025-09-15T17:36:19.963451Z",
    "warnings": [],
    "lifecycle": [
      {"type": "EMAIL_VERIFICATION_MESSAGE_SENT", "timestamp": "...", "fee": 0.03},
      {"type": "VALID_CODE_ENTERED", "timestamp": "...", "fee": 0}
    ]
  },
  "created_at": "2025-09-15T17:36:19.703719+00:00"
}

Status Values & Handling

StatusMeaningAction
"Approved"Code correct, no policy violationsEmail verified — proceed with your flow
"Failed"Code incorrectAsk user to re-enter. After 3 failures, resend a new code
"Declined"Code correct but policy violationInform user. Check email.warnings for reason
"Expired or Not Found"No pending codeCode expired (>5 min) or Send was never called. Resend

Error Responses

CodeMeaningAction
400Invalid request bodyCheck email and code format
401Invalid or missing API keyVerify x-api-key header
403Insufficient credits/permissionsCheck credits in Business Console
404Code expired or not foundResend a new code via Step 1

Response Field Reference

email Object

FieldTypeDescription
statusstring"Approved", "Failed", "Declined"
emailstringThe email address verified
is_breachedbooleanFound in known data breaches
breachesarrayBreach details: {name, domain, breach_date, data_classes, breach_emails_count}
is_disposablebooleanFrom a disposable/temporary provider
is_undeliverablebooleanCannot receive email
verification_attemptsintegerNumber of check attempts (max 3)
verified_atstringISO 8601 timestamp when verified (null if not)
warningsarrayRisk warnings: {risk, log_type, short_description, long_description}
lifecyclearrayEvent log: {type, timestamp, fee}

Warning Tags

TagDescriptionAuto-Decline
EMAIL_CODE_ATTEMPTS_EXCEEDEDMax code entry attempts exceededYes
EMAIL_IN_BLOCKLISTEmail is in blocklistYes
UNDELIVERABLE_EMAIL_DETECTEDEmail cannot be deliveredYes
BREACHED_EMAIL_DETECTEDFound in known data breachesConfigurable
DISPOSABLE_EMAIL_DETECTEDDisposable/temporary providerConfigurable
DUPLICATED_EMAILAlready verified by another userConfigurable

Warning severity levels: error (critical), warning (requires attention), information (informational).


Common Workflows

Basic Email Verification

1. POST /v3/email/send/   → {"email": "user@example.com"}
2. Wait for user to provide the code
3. POST /v3/email/check/  → {"email": "user@example.com", "code": "123456"}
4. If "Approved"            → email is verified
   If "Failed"              → ask user to retry (up to 3 attempts)
   If "Expired or Not Found"→ go back to step 1

Strict Security Verification

1. POST /v3/email/send/   → include signals.ip, signals.device_id, signals.user_agent
2. Wait for user to provide the code
3. POST /v3/email/check/  → set all *_action fields to "DECLINE"
4. If "Approved"  → safe to proceed
   If "Declined" → check email.warnings for reason, block or warn user

Utility Scripts

verify_email.py: Send and check email verification codes from the command line.

# Requires: pip install requests
export DIDIT_API_KEY="your_api_key"

python scripts/verify_email.py send user@example.com
python scripts/verify_email.py check user@example.com 123456 --decline-breached --decline-disposable

Can also be imported as a library:

from scripts.verify_email import send_code, check_code

send_result = send_code("user@example.com")
check_result = check_code("user@example.com", "123456", decline_breached=True)

平台分布

OpenClaw

73.18%
按下载量换算2,874

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

未展示

权限和风险

接触敏感数据

该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills