Token导航 LogoToken导航

Agent Skill · 研究检索

contact-research(联系研究)

contact-research 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

contact-research 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证信息还不明确,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 6,544。

总安装 21,812周安装 918GitHub Stars 11,683下载 7,638核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:contact-research(联系研究)
来源仓库:https://github.com/anthropics/knowledge-work-plugins
仓库路径:skills/contact-research
安装命令:
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill contact-research
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill contact-research

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

Contact Research 基于 Common Room 检索全面联系档案,支持按邮箱、社交账号或姓名+公司查找。返回包含活动历史、评分、网站访问记录和 CRM 字段的增强数据。可通过多种方式定位联系人,自动匹配最可靠路径并提供身份解析建议。需注意数据来源权限与隐私合规性,避免越权访问或泄露敏感信息。

contact-research 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

来源仓库内路径:skills/contact-research

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/anthropics/knowledge-work-plugins --skill cont…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

contact-research 怎么安装?

在终端执行 npx skills add https://github.com/anthropics/knowledge-work-plugins --skill contact-resear…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

contact-research 支持哪些 AI 工具?

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

contact-research 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

contact-research 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

contact-research 用的人多吗?

公开数据是累计安装 21,812 次,近一周安装 918 次,下载 7,638 次,GitHub 11,683 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

contact-research 安全吗?

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

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

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 来源仓库有 11,683 星,维护活跃度相对可查。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

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

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
contact-research

联系研究 · 本页

21,81211,683需要联网未明确通过

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

SKILL.md 原文

Contact Research

Retrieve a comprehensive contact profile from Common Room. Supports lookup by email, social handle, or name + company. Returns enriched data including activity history, Spark, scores, website visits, and CRM fields.

Step 1: Locate the Contact

Common Room supports multiple lookup methods — use whichever the user has provided:

What the user givesLookup method
Email addressLook up by email (most reliable)
LinkedIn, Twitter/X, or GitHub handleLook up by social handle — specify handle type explicitly
Name + companyIdentity resolution by name + org domain; present matches if ambiguous
Name onlySearch by name; if multiple matches, show a brief list and ask the user to confirm

If no match is found, respond: "Common Room doesn't have a record for this person." Do not speculate or fabricate profile data.

Step 2: Fetch Contact Fields

Use the Common Room object catalog to see available field groups and their contents. For full profiles, request all groups. For targeted questions, request only what's relevant.

Key field groups to know about:

  • Scores — always return as raw values or percentiles, never labels
  • Recent activity — use Contact Initiated filter (last 60 days) for their actions, not your team's
  • Website visits — total count + specific pages (last 12 weeks)
  • Spark — retrieve all Sparks when tracking engagement evolution over time

Step 3: Run Spark Enrichment (If Available)

If Spark is available, use it. Spark provides:

  • Professional background and job history
  • Social presence and influence signals
  • Persona classification: Champion, Economic Buyer, Technical Evaluator, End User, or Gatekeeper
  • Inferred role in the buying process

If Spark is unavailable but real activity data exists (recent actions, website visits, community engagement), infer a persona from those signals. If neither Spark nor activity data is available, classify as Unknown — do not guess a persona from title alone.

Retrieve all Sparks (not just the most recent) when the user wants to understand how this contact's engagement has evolved over time.

Step 4: Assess Account Context

Pull an abbreviated account snapshot for this contact's parent company. Note:

  • Open opportunities, expansion signals, or churn risk at the account level
  • Whether other contacts at this company are also active
  • How this person's engagement compares to their colleagues

Step 5: Identify Conversation Angles

Based on activity and signals, surface the strongest 2–3 hooks:

  • A recent Contact Initiated activity (community post, product event, support ticket)
  • A specific web page they visited recently — especially if it signals evaluation intent
  • A job change, promotion, or company news
  • Their Spark persona and what that suggests about communication style
  • Their role in a known active deal

Output Format

Only include sections where data was actually returned. Omit sections with no data rather than filling them with guesses.

When data is rich:

## [Contact Name] — Profile

**Overview**
[2 sentences: who they are, their role, and relationship status]

**Details**
- Title: [title]
- Company: [company]
- Email: [email]
- LinkedIn: [URL]
- Other profiles: [Twitter/X, GitHub, CRM link if available]

**Scores** [If scores returned]
[All scores as raw values or percentiles]

**Recent Activity** (last 60 days) [If activity returned]
[3–5 bullets with dates]

**Website Visits** (last 12 weeks) [If visit data exists]
[Total visit count + list of pages visited]

**Spark Profile** [If Spark data is non-null]
[Persona type, background summary, influence signals]

**Segments** [If segments returned]
[List of segment names this contact belongs to]

**Account Context**
[1–2 sentences on their company's status]

**Conversation Starters**
[2–3 specific, signal-backed openers]

When data is sparse (e.g., only name, title, email, tags returned; sparkSummary is null):

## [Contact Name] — Profile (Limited Data)

**Data available:** [List exactly what Common Room returned]

[Present only the returned fields]

**Web Search**
[Any findings from searching their name + company]

**Note:** Common Room has limited data on this contact. No activity history, scores, or Spark profile available. I can run deeper web searches or look up their company for additional context.

Do not generate conversation starters, persona inferences, or engagement assessments from sparse data. These require real signals.

Quality Standards

  • Lookup must use the correct method for the input type — don't guess on email vs. handle
  • Scores as raw/percentile only — never labels
  • Contact Initiated activity (last 60 days) is the primary engagement signal — lead with it
  • If Spark is unavailable, say so — don't fabricate a persona from title alone
  • Flag any contact where the most recent activity is older than 30 days

Reference Files

  • references/contact-signals-guide.md — full field descriptions, Spark persona guide, and conversation starter principles

平台分布

Codex

35.46%
按下载量换算2,708

Claude

32.33%
按下载量换算2,469

Cursor

18.26%
按下载量换算1,395

Gemini CLI

10.03%
按下载量换算766

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

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

继续浏览同类 Skills