一键在 Manus 中运行任何 Skill

verify-email

星标1

分支0

更新时间2026年4月30日 15:25

Validate a single email address via Hunter Email-Verifier. Use when the user has an address (handed to them, scraped, guessed) and wants a deliverability + confidence read before sending outreach. Returns Hunter's verdict (deliverable / risky / undeliverable / unknown), score, and the disposable / role / accept-all flags. Does not write to the CRM unless asked.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

danielrosehill

danielrosehill/Claude-Career-Plugin

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

Verify Email

Wraps Hunter's Email-Verifier. One address in, one verdict out.

Inputs

$ARGUMENTS:

Required: <email> — first positional.
Optional: --update-crm — if the email matches a row in ${CAREER_WORKSPACE}/crm/contacts.md, update the verified and last-verified columns.

Procedure

1. Sanity check input

If <email> is malformed (no @, no TLD), bail with a one-line error — don't spend a Hunter credit on garbage.

2. Call Hunter

Call Email-Verifier with the address. Capture: result, score, disposable, webmail, mx_records, smtp_check, accept_all, block.

3. Render

Compact summary:

email:        jane.doe@acme.com
verdict:      deliverable
score:        92
flags:        webmail=no, accept_all=no, disposable=no
mx / smtp:    yes / yes

Add a one-line interpretation:

deliverable + score ≥ 80 → safe to send.
risky or score 50–79 → send only if you have a fallback channel.
undeliverable / block → do not send.
accept_all=yes → Hunter can't truly verify; treat as risky.

4. Optional: update CRM row

If --update-crm:

Load ${CAREER_WORKSPACE}/crm/contacts.md (resolve CAREER_WORKSPACE per the standard order: env var → config.json WORKING_FOLDER → $PWD). Find the row whose email matches. Update verified (yes/no/risky) and append last-verified=<YYYY-MM-DD> to the notes column. If no row matches, say so — don't insert.

Failure modes

Hunter MCP not loaded → bail with: enable the hunter MCP via this plugin's .mcp.json (set HUNTER_API_KEY).
429 rate limit → surface verbatim, stop.
Address not in standard format → bail before calling Hunter.

Idempotency

Re-running on the same address re-hits Hunter (results can change as Hunter's index updates). --update-crm is overwrite-in-place, never duplicates rows.

同仓库更多 Skills

同仓库

bulk-verify-crm

danielrosehill/Claude-Career-Plugin

Sweep all (or a filtered subset of) email addresses in the workspace CRM and re-verify them via Hunter Email-Verifier. Use periodically — people change jobs, addresses go stale, accept-all status changes. Updates the `verified` and `last-verified` columns in `crm/contacts.md` and prints a summary of what flipped.

2026-04-301

detect-mcps

danielrosehill/Claude-Career-Plugin

Scan the user's existing Claude Code plugins and MCP servers to detect capabilities the career plugin needs (email send, transcription, calendar/tasks, semantic store, CRM). For each capability, decide whether to reuse an already-installed plugin/MCP, install a recommended companion plugin, or add an MCP server. Writes the resolution map to ${CAREER_DATA_DIR}/config.json under a `capabilities` block. Invoked from /career:onboard before install-companion-plugins so we don't double up on capabilities the user already has.

2026-04-301

enrich-contact

danielrosehill/Claude-Career-Plugin

Enrich an existing CRM contact with Hunter Combined-Enrichment — pulls role, seniority, department, social handles, and the contact's company facts in one call. Use to flesh out a thinly-populated CRM row before drafting outreach or prepping for a meeting. Operates on an email address from the CRM; updates the row in place.

2026-04-301

find-email-by-name

danielrosehill/Claude-Career-Plugin

Given a person's name and their company (name or domain), return Hunter's best guess at their email address with a confidence score. Use when the user already knows who they want to reach and just needs the address. Differs from find-contact (which lists candidates at a company) — this is targeted at a single named person.

2026-04-301

vector-conflict-check

danielrosehill/Claude-Career-Plugin

For CONTEXT_STORE=pinecone — verify the index against the local workspace. Flags vectors whose source file was deleted, renamed, or content-changed (hash mismatch), and surfaces vectors whose content contradicts current ground-truth (stale claims, closed engagements, outdated targets). Proposes deletes/re-embeds; never silently mutates the index.

2026-04-281

vector-init-applications

danielrosehill/Claude-Career-Plugin

First-run scaffold of a vector-store namespace dedicated to application/outreach tracking. Creates the `applications` namespace in the configured index, sets the metadata schema (company, role, status, applied_date, last_touch, source_path, stage), seeds it from crm/outreach.md + crm/opportunities.md, and registers it in config. Idempotent — re-running detects existing namespace and offers reseed or skip.

2026-04-281

name	verify-email
description	Validate a single email address via Hunter Email-Verifier. Use when the user has an address (handed to them, scraped, guessed) and wants a deliverability + confidence read before sending outreach. Returns Hunter's verdict (deliverable / risky / undeliverable / unknown), score, and the disposable / role / accept-all flags. Does not write to the CRM unless asked.
disable-model-invocation	false
allowed-tools	Read, Edit, mcp__jungle-personal__hunter__Email-Verifier

Verify Email

Wraps Hunter's Email-Verifier. One address in, one verdict out.

Inputs

$ARGUMENTS:

Required: <email> — first positional.
Optional: --update-crm — if the email matches a row in ${CAREER_WORKSPACE}/crm/contacts.md, update the verified and last-verified columns.

Procedure

1. Sanity check input

If <email> is malformed (no @, no TLD), bail with a one-line error — don't spend a Hunter credit on garbage.

2. Call Hunter

Call Email-Verifier with the address. Capture: result, score, disposable, webmail, mx_records, smtp_check, accept_all, block.

3. Render

Compact summary:

email:        jane.doe@acme.com
verdict:      deliverable
score:        92
flags:        webmail=no, accept_all=no, disposable=no
mx / smtp:    yes / yes

Add a one-line interpretation:

deliverable + score ≥ 80 → safe to send.
risky or score 50–79 → send only if you have a fallback channel.
undeliverable / block → do not send.
accept_all=yes → Hunter can't truly verify; treat as risky.

4. Optional: update CRM row

If --update-crm:

Failure modes

Hunter MCP not loaded → bail with: enable the hunter MCP via this plugin's .mcp.json (set HUNTER_API_KEY).
429 rate limit → surface verbatim, stop.
Address not in standard format → bail before calling Hunter.

Idempotency

Re-running on the same address re-hits Hunter (results can change as Hunter's index updates). --update-crm is overwrite-in-place, never duplicates rows.