Token导航 LogoToken导航TokenDH.com
研究检索权限需确认github未标认证来源可访问许可证需确认审计通过

discovery-call-prep发现通话准备

Agent Skill

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

总安装

1

周安装

8

GitHub Stars

283

下载量

65
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:discovery-call-prep(发现通话准备)
来源仓库:https://github.com/mohitagw15856/pm-claude-skills
仓库路径:skills/discovery-call-prep
安装命令:
npx skills add https://github.com/mohitagw15856/pm-claude-skills --skill discovery-call-prep
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/mohitagw15856/pm-claude-skills --skill discovery-call-prep

简介

discovery-call-prep 用于生成完整的发现通话简报,包含研究摘要、通话假设、结构化问题及成功标准。

  • 适用于产品团队在启动客户访谈前的准备工作,尤其适合 PM 或销售工程师梳理调研框架。
  • 输入包括公司名称、联系人角色、已知上下文及解决方案简介,输出为可执行的话术清单。
  • 安装时需注意该技能依赖外部信息获取能力,建议提前确认 API 调用权限与数据源可靠性。
  • 适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

SKILL.md

Discovery Call Prep Skill

Produces a complete discovery call brief — research summary, call hypothesis, structured questions, and success criteria — so every call starts with context and ends with a clear next step.

Required Inputs

  • Prospect company name
  • Contact name and role
  • Any known context (how they found you, prior interaction)
  • Your product/solution (one line)
  • Call duration (15 / 30 / 45 / 60 min)

Output Structure


Discovery Call Brief

Prospect: [Company] | Contact: [Name, Title] | Duration: [X min]


Research Summary

  • What they do: [Product/service, customer, business model]
  • Size: [Headcount, revenue if public]
  • Stage: [Startup / Scaleup / Enterprise]
  • Recent news: [Funding, launches, leadership changes — last 90 days]
  • Contact background: [Role tenure, previous companies, LinkedIn activity]
  • Likely priorities for someone in this role: [Based on title and stage]

Call Hypothesis

Before the call write your best guess:

  • Their most likely pain: [What someone in this role at this company probably has]
  • Why they would care about us: [Specific connection to your value]
  • Biggest risk to the deal: [What might make this not a fit]

Write it down — then test it on the call.


Call Agenda

"Here is what I was thinking for our [X] minutes:

  • 2 min: Quick intros
  • min: Learn more about your situation
  • min: Share how we have helped similar companies
  • 5 min: Next steps Does that work? Anything specific you would like to cover?"

Discovery Questions

Open with context (not a pitch):

  • "What prompted you to take this call today?"
  • "What does [relevant area] look like for you at the moment?"

Go deeper on pain:

  • "How long has [problem] been an issue?"
  • "What have you tried to solve it?"
  • "What is the impact of not solving this?"

Understand buying context:

  • "Who else would be involved in a decision like this?"
  • "Have you looked at other solutions?"
  • "Is there a reason you are exploring this now?"

Qualify on budget:

  • "Have you set aside budget for this kind of initiative?"

Close discovery:

  • "Based on what you have told me, it sounds like [summary]. Is that right?"

Success Criteria

This call is successful if we leave with:

  • Understanding of specific pain and business impact
  • Knowledge of buying process and key stakeholders
  • A clear agreed next step (demo / proposal / intro)
  • Sense of timeline

This call is NOT successful if we only pitched and got "sounds interesting, send me some info."


Suggested Next Step

"Based on what we discussed, the logical next step would be [specific]. Does [day/time] work?"

Quality Checks

  • Research summary includes recent news (last 90 days) — not just LinkedIn bio
  • Call hypothesis is written before the call (not post-rationalised after)
  • Discovery questions progress from context → pain → business impact → buying process
  • Success criteria define what "not successful" looks like (not just the ideal outcome)
  • A specific next step is proposed (not "let's stay in touch")

Example Trigger Phrases

  • "Prepare me for a discovery call with [company/contact]"
  • "Build a call brief for my meeting with [name] at [company]"
  • "What questions should I ask in a discovery call for [use case]?"

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

35.07%
按下载量换算23

Claude

28.11%
按下载量换算18

Cursor

18.35%
按下载量换算12

Gemini CLI

8.74%
按下载量换算6

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

权限需确认

当前来源未能明确判断权限范围,默认进入异常复核队列。

安装前确认

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

来源信息

继续浏览同类 Skills