jernejcicorbin-hub

Lead Contact Finder

商业运营v1.0.0
作者:jernejcicorbin-hub更新于 2026-05-12contact-discovery@clawhub_jernejcicorbin-hub/contact-discovery
销售助手#Web Search#Email

据 AlphaMoat 统计,截至 2026-10,Lead Contact Finder 累计下载 9,094 次、获 1 个星标,按累计下载量在本次参与排名的 10,914 个 AI 技能中排名第 3,042 位,在「商业运营」分类(873 个)中排名第 247 位。

列表默认按累计下载量排序,也可按星标排序;详情页排名按累计下载量计算。

累计下载
9,094
星标
1
全站下载量排名
#3,042
全站前 28% · 「商业运营」前 29%
平台累计下载星标评论
ClawHub ↗8,7261-
SkillHub ↗9,0941—

各平台的计数口径不同,统计时间不一致。

这个技能是做什么的

该技能在公开网络证据中搜索邮箱、联系页面、媒体/支持入口以及公司邮箱格式线索,并返回判定结果(如 public_email_found、not_found)与来源 URL。它需要 PRISMFY_API_KEY 以及 curl、jq 二进制,并强调不得编造私人联系数据。

资料发布于 2026-10-27

可以用来做什么

  • 在外联前查找公开邮箱或联系路径
  • 整理公司邮箱格式线索供人工复核
  • 导出 JSON 形式的联系人发现报告

什么时候用

  • 用户需要公开邮箱或公开联系方式时
  • 外联前卡在如何触达某个线索时
  • 想确认某人是否有公开邮箱轨迹时

示例提示词

以下是根据技能文档生成的示例,不代表实际运行结果。

查找 Vercel 的 Guillermo Rauch 的公开联系信息
确认 Acme 是否有公开的媒体或支持联系页

月度数据趋势

累计下载9,094
8,0958,6329,1682026-06 · 累计下载 8,1692026-07 · 累计下载 8,4002026-08 · 累计下载 8,5032026-09 · 累计下载 8,7682026-10 · 累计下载 9,09426-0626-0926-10
星标1
0122026-06 · 星标 12026-07 · 星标 12026-08 · 星标 12026-09 · 星标 12026-10 · 星标 126-0626-0926-10

2026-09 起统计方法调整:同名技能按作者分别统计,并覆盖全部技能。图中虚线为调整前的月份,与之后的数据不直接比较,也不计算跨越调整的增长。

月份累计下载环比星标
2026-109,094—1
2026-098,768—1
2026-088,503+1.2%1
2026-078,400+2.8%1
2026-068,169—1

SKILL.md 原文

以下是作者发布的原始文件,按纯文本显示,本站未做修改或审核;其中的链接不可点击,命令请核实后再运行。抓取于 2026-10-23。

7.1 KB · ClawHub v1.0.0
---
name: contact-discovery
description: >
  Find public contact details for a person or company using Prismfy-powered web search.
  Use when a user wants a public email, contact path, press/support page, or company email-format clue before outreach.
version: 1.0.0
metadata:
  openclaw:
    requires:
      env:
展开全部(共 248 行)
        - PRISMFY_API_KEY
      bins:
        - curl
        - jq
    primaryEnv: PRISMFY_API_KEY
    emoji: "📬"
    homepage: https://prismfy.io
---

# Contact Discovery

Use this skill when you need to find public contact details for a company or a specific person at that company.

Why it helps:
- finds public emails when they are actually exposed on the public web,
- finds contact paths when no direct email is visible,
- surfaces company email-format clues without guessing,
- keeps the agent from inventing private contact data.

Best for:
- pre-outreach contact discovery,
- finding public press/support/team contact pages,
- checking whether a person has a public email trail,
- finding company email-format clues for later human review.

Need a key?
- Get free search access and your API key at: https://prismfy.io

## Setup

1. Install the skill:
```bash
openclaw skills install contact-discovery
```

2. Add your Prismfy API key:
```bash
export PRISMFY_API_KEY="ss_live_your_key_here"
```

To keep it after restart:
```bash
echo 'export PRISMFY_API_KEY="ss_live_your_key_here"' >> ~/.bashrc
source ~/.bashrc
```

Preflight:
- `PRISMFY_API_KEY` is set
- `curl` and `jq` are installed

Advanced setup:
- if quota lives on a different endpoint than search, set `PRISMFY_API_ROOT` or `PRISMFY_ME_URL`

3. Verify API access:
```bash
cd ~/.openclaw/workspace/skills/contact-discovery
bash contact-find.sh --quota
```

4. Quick smoke test:
```bash
cd ~/.openclaw/workspace/skills/contact-discovery
bash contact-find.sh --company "Vercel" --query-family company
```

5. Export a JSON report:
```bash
cd ~/.openclaw/workspace/skills/contact-discovery
bash contact-find.sh --person "Guillermo Rauch" --company "Vercel" --query-family all --out contact_discovery_report.json
```

Optional automation:
```bash
# Run from this skill directory:
# ~/.openclaw/workspace/skills/contact-discovery

cp -r hooks/contact-discovery ~/.openclaw/hooks/
find ~/.openclaw/hooks/contact-discovery -maxdepth 1 -type f | sort
openclaw hooks enable contact-discovery
openclaw hooks list
```

## When to Use
Use this skill when:
- a user asks for a public email or public contact method,
- a user wants a contact path for a person or company,
- the next step is outreach and contact discovery is the blocker,
- a lead already exists and the missing piece is how to reach them.

## When NOT to Use
Avoid using this skill when:
- the task is lead qualification rather than contact discovery,
- the user wants private or guessed contact data,
- the task only needs company/person verification,
- there is no person, company, or domain anchor at all.

## Inputs
- `--company` (optional)
- `--domain` (optional)
- `--person` (optional)
- `--role` (optional)
- `--query-family` (optional: `identity|direct|company|pattern|all`)
- at least one of `--company`, `--domain`, or `--person` is required

Family notes:
- person-only mode is strongest with `direct`, `identity`, or `all`
- if `company` or `pattern` is used with person-only input, the helper falls back to weaker public-web clues and should be treated as lower confidence

## Outputs
Primary chat output:
- short verdict in plain language,
- `public_email_found | contact_path_found | company_contact_found | company_email_pattern_found | not_found | ambiguous`,
- best public contact clue,
- one concrete source URL.

Optional artifact output:
- JSON when the user asks for a file, export, or machine-readable report.
- Use `--out <file>` to write the report to disk.

If JSON artifact is produced, required fields are:
- `timestamp_utc`
- `skill_version`
- `entity_type`
- `identity_status`
- `contact_verdict`
- `summary`
- `public_emails[]`
- `contact_paths[]`
- `email_pattern_clues[]`
- `source_urls[]`
- `run_failure_code`

## Execution
1. Resolve identity first:
   - canonical company domain if possible,
   - person + company match if person-focused.
2. Run Prismfy query families in this order:
   - `identity`
   - `direct`
   - `company`
   - `pattern`
3. Return the strongest safe verdict:
   - `public_email_found`
   - `contact_path_found`
   - `company_contact_found`
   - `company_email_pattern_found`
   - `not_found`
   - `ambiguous`
4. Reply in chat first.
5. Emit JSON only when requested or when `--out` is used.

Command examples:
```bash
# Check quota / connectivity
bash contact-find.sh --quota

# Company contact discovery
bash contact-find.sh --company "Vercel" --query-family company

# Person + company contact discovery
bash contact-find.sh --person "Guillermo Rauch" --company "Vercel" --query-family all

# Export a report
bash contact-find.sh --person "Guillermo Rauch" --company "Vercel" --query-family all --out contact_discovery_report.json
```

Execution contract:
- preferred mode: balanced
- source cap: up to 5 URLs per query
- default chat mode: concise, human-readable, no raw JSON dump
- only treat an email as found if it appears explicitly in public evidence
- do not infer a private email from a pattern clue alone
- strongest verdicts come from `--query-family all`
- human review is still recommended before high-value outreach

## Query families

### `identity`
- official site
- contact/about/team pages
- person + company exact match

### `direct`
- person + company + email/contact
- person + company + author/press
- person + domain clue

### `company`
- company or domain contact pages
- press/support/help/team pages
- general company contact email traces
- in person-only mode, falls back to public contact/profile page discovery

### `pattern`
- company email format pages or mentions
- domain email format clues
- pattern-only evidence for later review
- in person-only mode, only yields weak clue discovery and should stay conservative

## Failure Handling
Use these failure codes:
- `PRISMFY_UNAVAILABLE`
- `PRISMFY_INVALID_RESPONSE`
- `IDENTITY_UNCLEAR`
- `NO_PUBLIC_EVIDENCE`
- `RATE_LIMIT_OR_TIMEOUT`

Handling guidance:
- If Prismfy is unavailable, say so explicitly.
- If identity is unclear, mark `ambiguous`.
- If only a pattern clue exists, say that clearly and do not present it as a real email.
- Never invent or guess a personal email.

## Response Style
- In normal chat, do not lead with JSON.
- Lead with the verdict.
- Then show the best public email or best contact path.
- Keep it compact.
- Mention a report filename only if `--out` created one.

## Safety
- Do not expose API keys.
- Do not guess personal emails from patterns.
- Do not claim a contact method exists unless backed by public evidence.
- Do not present likely deliverability as confirmed deliverability.

## Minimal Example
Input:
- `--person`: `Guillermo Rauch`
- `--company`: `Vercel`

Default chat output:
- `Contact path found.`
- `1. Identity: canonical domain = vercel.com`
- `2. Evidence: emails=0, direct_hits=2, company_hits=3, pattern_hits=1, official_hits=2`
- `3. Path: https://vercel.com/contact`
- `4. Source: https://vercel.com/contact`

「商业运营」分类下的热门技能

标书写作专家【百炼标书】商业运营

百炼®标书是一个面向投标场景标书写作的skill,可以帮用户完成四件事:解读招标文件、生成投标文件、审查投标文件合规风险以及标书查重。它适合用自然语言直接写作,用户只要提供文件和需求,就能拿到解读结果、成品标书、审查报告、查重报告。百炼®标书官网:https://biaoshu.zhiliaobiaoxun.com

↓ 70.7万★ 61u_62be253f
AdMapix广告投放工具商业运营

AdMapix广告原始数据层,广告创意/应用/排名/下载收入

↓ 30.9万★ 1u_8ee34d77
全国招标中标查询及分析【知了标讯】商业运营

知了标讯:查询和分析招标、中标、供应商与采购市场信息。

↓ 21.4万★ 14user_98035bfb
招标中标查询及分析服务商业运营

通过知了标讯接口查询和分析招投标相关信息。

↓ 12.1万★ 16user_98035bfb
标书审查【喜鹊标书】商业运营

喜鹊标书审查|让投标风险看得见、查得清、改得准 投标文件准备好了,还有哪些遗漏和隐患?喜鹊标书审查对照招标要求,检查投标文件中的响应缺漏、内容矛盾和潜在风险,帮助您在提交前发现问题、明确修改重点。 - 问题一目了然:区分已确认风险与待核实事项,清晰呈现问题位置、具体表现及潜在影响。 - 审查有据可查:关联招标条款与投标内容,让您看清“要求是什么、哪里存在问题、判断依据是什么”。 - 原文快速定位:结合页码、检索线索和证据截图,减少来回翻找,方便逐项核对。 - 完整报告可交付:提供 Word 审查报告及审查版 PDF,便于团队复核、修改和留档。 支持 PDF、DOCX 及多附件审查。先检查文件,再展示价格并按次付费;支持随时查询进度、继续已付款任务和补领报告,让每一次审查都有清晰结果。 https://www.xiquebiaoshu.com/?source=skillhub](https://www.xiquebiaoshu.com/?source=bid-review-pay

↓ 10.5万★ 1u_84923c62
PollyReach商业运营

为 AI agent 提供电话号码并代办电话事务的技能。

↓ 10.2万★ 56PollyReach
商品图商业运营

将真实产品照片制作成影棚级电商主图、场景图或面向市场平台的高清商品图。这款 AI 商品图工作室用于商品图片处理和电商图片编辑,可替换背景、改善光效、搭建场景。它以原图中的商品外观特征为依据,从一张手机随拍就能做出白底主图、生活场景图和高级广告图。适用于亚马逊白底产品图、淘宝主图、Shopify 产品大图和社交媒体商品图。从一张产品照片出发,组合多张参考图,或在选定草稿上做定向精修,完成适合上架使用的成品;生活场景图和广告图也能直接用作商品详情页图片。

↓ 10.2万★ 10user_87b8e34f
会员体系搭建商业运营

【零一数科·出品】会员体系搭建(免费版)。为私域用户设计会员体系搭建,产出会员等级成长表、积分获取消耗规则表、权益配置矩阵、积分财务测算表四件套。适用于会员积分体系设计、会员等级阶梯、成长值规则、权益配置、积分获取与消耗、积分财务测算、私域会员运营。

↓ 9.7万★ 8u_c19e970c

jernejcicorbin-hub 的其他技能

数据月份:2026-10 · 下载/星标数聚合自公开技能注册库(ClawHub、SkillHub),按月更新。口径说明见数据方法。