360 Secure SkillHub
360 安全技能中心

Mailcheck

本 Skill 借助 OOMOL 的 oo CLI 调用 mailcheck 连接器，按需执行 get_status、validate_domain、verify_email 三个动作：查询账户与用量信息，返回邮箱可投递性以及域名风险、MX 等信号。运行前先用 schema 子命令查看动作契约再构造 JSON 参数，凭据由服务端注入，用户无需管理令牌。

oomol
oomol
热度 50.91
最近更新 2026-09-15 12:22:52
分类：数据依赖：代码执行 / 第三方 API应用场景：数据处理 / API 集成

安装技能

复制下面的话术发给你的 Agent，它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill： npx secure-skills-cli add oo-mailcheck
Metadata
name
oo-mailcheck
description
Mailcheck (usercheck.com). Use this skill for ANY Mailcheck request — searching and reading data. Whenever a task involves Mailcheck, use this skill instead of calling the API directly.
allowed-tools
["Bash(oo *)"]
metadata
{"title":"Mailcheck","author":"OOMOL","version":"1.0.3","services":["mailcheck"],"icon":"https://static.oomol.com/logo/third-party/Mailcheck.svg"}

Mailcheck

Operate Mailcheck through your OOMOL-connected account. This skill calls the mailcheck connector with the oo CLI; OOMOL injects credentials server-side, so you never handle raw tokens.

Running an action

Assume the user has already installed the oo CLI, signed in, and connected Mailcheck. Do not run oo auth login or open the connection URL proactively — just run the action. Fall back to First-time setup only when a command actually fails with an auth or connection error.

1. Inspect the contract to get the authoritative input/output schema before building a payload:

oo connector schema "mailcheck" --action "<action_name>"

2. Run the action with a JSON payload that matches the input schema:

oo connector run "mailcheck" --action "<action_name>" --data '<json>' --json
  • --data takes a JSON object string or @path/to/file.json; omit it to send {}.
  • The response is { "data": ..., "meta": { "executionId": "..." } }; the execution id lives under meta.executionId.

Each action is listed below with a one-line description; actions that change state carry a [write] or [destructive] tag. Before constructing --data, fetch the action's live schema with oo connector schema to get its authoritative input fields.

Available actions

  • get_status — Retrieve UserCheck account information, plan details, and current API usage.
  • validate_domain — Validate a domain and return UserCheck domain-level risk and MX signals.
  • verify_email — Validate a single email address and return UserCheck deliverability and risk signals.

Safety

  • Untagged actions are reads (get / list / search) — safe to run directly.
  • Actions tagged [write] change Mailcheck state — confirm the exact payload and effect with the user before running.
  • Actions tagged [destructive] remove or overwrite data — always confirm the target and get explicit approval first.

First-time setup

These are one-time steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.

  • oo: command not found — install the oo CLI (other platforms: https://cli.oomol.com/install-guide.md):

    curl -fsSL https://cli.oomol.com/install.sh | bash    # macOS / Linux

    irm https://cli.oomol.com/install.ps1 | iex           # Windows PowerShell

  • Not signed in / authentication error — sign in to your OOMOL account once:

    oo auth login

  • scope_missing / credential_expired / app_not_ready / app_not_found — Mailcheck is not connected, or the connection expired or lacks a scope. Connect once (auth type: API key) at:

    https://console.oomol.com/app-connections?provider=mailcheck

  • HTTP 402 / OOMOL_INSUFFICIENT_CREDIT — billing stop. Recharge at https://console.oomol.com/billing/token-recharge before retrying.

Resources