New: Earn 20% as an AgentAlley affiliate. Share your link and earn on every sale you refer. Join now New: Earn 20% as an affiliate. Join now

Prepare a structured discovery call plan for any prospect

Discovery Call Prep Skill

by mohitagw15856 · MIT license · ★ 1,395 on GitHub · updated Sep 23

Discovery Call Prep Skill cover

Prepare a structured discovery call plan for any prospect. Use when asked to prepare for a sales call, discovery call, prospect meeting, or first call with a potential customer.

---
name: discovery-call-prep
description: "Prepare a structured discovery call plan for any prospect. Use when asked to prepare for a sales call, discovery call, prospect meeting, or first call with a potential customer. Produces a call brief with research, hypotheses, questions, and success criteria."
---

# 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

Overview

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.

Manual install (npx, ZIP)
Claude Codenpx skills add mohitagw15856/pm-claude-skills --skill discovery-call-prep -g -a claude-code
Claude Code (manual)mkdir -p ~/.claude/skills && curl -sL https://codeload.github.com/mohitagw15856/pm-claude-skills/tar.gz/f6ca79348c55 \ | tar -xz -C ~/.claude/skills --strip-components=2 pm-claude-skills-f6ca79348c55/skills/discovery-call-prep
Windows (PowerShell)New-Item -ItemType Directory -Force "$HOME\.claude\skills" | Out-Null; Invoke-WebRequest "https://m.agentalley.io/zip/555c08b79717d5b3c2da/discovery-call-prep.zip" -OutFile "$env:TEMP\discovery-call-prep.zip"; Expand-Archive "$env:TEMP\discovery-call-prep.zip" -DestinationPath "$HOME\.claude\skills" -Force
Claude.ai / desktopDownload the ZIP and upload it under Settings → Capabilities → Skills.
Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

  • SKILL.md4.4 KB
Read the files here
mohitagw15856/f6ca7931 file
SKILL.md
Show the full text114 lines

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")

Anti-Patterns

  • Do not write the call hypothesis after the call — hypotheses written post-hoc are rationalisations, not testable predictions
  • Do not open with a product pitch before establishing the prospect's problem — leading with pitch signals you are not there to learn, which closes discovery conversations
  • Do not use closed questions in the discovery phase ("Do you have this problem?") — they produce yes/no answers that confirm bias rather than reveal pain
  • Do not skip the "not successful" definition in success criteria — a call that ends with "send me more info" feels like progress but is not a qualified next step
  • Do not treat all prospect research equally — recent news (last 90 days) is more relevant to call context than static company facts from LinkedIn

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]?"
1---
2name: discovery-call-prep
3description: "Prepare a structured discovery call plan for any prospect. Use when asked to prepare for a sales call, discovery call, prospect meeting, or first call with a potential customer. Produces a call brief with research, hypotheses, questions, and success criteria."
4---
5 
6# Discovery Call Prep Skill
7 
8Produces 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.
9 
10## Required Inputs
11- **Prospect company name**
12- **Contact name and role**
13- **Any known context** (how they found you, prior interaction)
14- **Your product/solution** (one line)
15- **Call duration** (15 / 30 / 45 / 60 min)
16 
17## Output Structure
18 
19---
20 
21# Discovery Call Brief
22**Prospect:** [Company] | **Contact:** [Name, Title] | **Duration:** [X min]
23 
24---
25 
26### Research Summary
27- What they do: [Product/service, customer, business model]
28- Size: [Headcount, revenue if public]
29- Stage: [Startup / Scaleup / Enterprise]
30- Recent news: [Funding, launches, leadership changes — last 90 days]
31- Contact background: [Role tenure, previous companies, LinkedIn activity]
32- Likely priorities for someone in this role: [Based on title and stage]
33 
34---
35 
36### Call Hypothesis
37Before the call write your best guess:
38- **Their most likely pain:** [What someone in this role at this company probably has]
39- **Why they would care about us:** [Specific connection to your value]
40- **Biggest risk to the deal:** [What might make this not a fit]
41 
42Write it down — then test it on the call.
43 
44---
45 
46### Call Agenda
47"Here is what I was thinking for our [X] minutes:
48- 2 min: Quick intros
49- [X] min: Learn more about your situation
50- [X] min: Share how we have helped similar companies
51- 5 min: Next steps
52Does that work? Anything specific you would like to cover?"
53 
54---
55 
56### Discovery Questions
57 
58Open with context (not a pitch):
59- "What prompted you to take this call today?"
60- "What does [relevant area] look like for you at the moment?"
61 
62Go deeper on pain:
63- "How long has [problem] been an issue?"
64- "What have you tried to solve it?"
65- "What is the impact of not solving this?"
66 
67Understand buying context:
68- "Who else would be involved in a decision like this?"
69- "Have you looked at other solutions?"
70- "Is there a reason you are exploring this now?"
71 
72Qualify on budget:
73- "Have you set aside budget for this kind of initiative?"
74 
75Close discovery:
76- "Based on what you have told me, it sounds like [summary]. Is that right?"
77 
78---
79 
80### Success Criteria
81This call is successful if we leave with:
82- Understanding of specific pain and business impact
83- Knowledge of buying process and key stakeholders
84- A clear agreed next step (demo / proposal / intro)
85- Sense of timeline
86 
87This call is NOT successful if we only pitched and got "sounds interesting, send me some info."
88 
89---
90 
91### Suggested Next Step
92"Based on what we discussed, the logical next step would be [specific]. Does [day/time] work?"
93 
94## Quality Checks
95 
96- [ ] Research summary includes recent news (last 90 days) — not just LinkedIn bio
97- [ ] Call hypothesis is written before the call (not post-rationalised after)
98- [ ] Discovery questions progress from context → pain → business impact → buying process
99- [ ] Success criteria define what "not successful" looks like (not just the ideal outcome)
100- [ ] A specific next step is proposed (not "let's stay in touch")
101 
102## Anti-Patterns
103 
104- [ ] Do not write the call hypothesis after the call — hypotheses written post-hoc are rationalisations, not testable predictions
105- [ ] Do not open with a product pitch before establishing the prospect's problem — leading with pitch signals you are not there to learn, which closes discovery conversations
106- [ ] Do not use closed questions in the discovery phase ("Do you have this problem?") — they produce yes/no answers that confirm bias rather than reveal pain
107- [ ] Do not skip the "not successful" definition in success criteria — a call that ends with "send me more info" feels like progress but is not a qualified next step
108- [ ] Do not treat all prospect research equally — recent news (last 90 days) is more relevant to call context than static company facts from LinkedIn
109 
110## Example Trigger Phrases
111- "Prepare me for a discovery call with [company/contact]"
112- "Build a call brief for my meeting with [name] at [company]"
113- "What questions should I ask in a discovery call for [use case]?"
114 
View all files on GitHub →

Details

Updated
Sep 23, 2026
License
MIT
Stars on the repo
★ 1,395
Checked
Source
mohitagw15856/pm-claude-skills ↗
Creator
mohitagw15856 · 193 listings
View creator

Made with discovery-call-prep

Discovery Call Prep Skill — Galaxy 3D — fly through all 1170 skills as a glowing constellation you orbit and click into (from the mohitagw15856/pm-claude-skills README)
Discovery Call Prep Skill — Galaxy 3D — fly through all 1170 skills as a glowing constellation you orbit and click into (from the mohitagw15856/pm-claude-skills README)

by mohitagw15856

Discovery Call Prep Skill — PM Skills Wrapped — your practice turned into a shareable, Spotify-Wrapped-style story (from the mohitagw15856/pm-claude-skills README)
Discovery Call Prep Skill — PM Skills Wrapped — your practice turned into a shareable, Spotify-Wrapped-style story (from the mohitagw15856/pm-claude-skills README)

by mohitagw15856

Similar skills

See all →
SkillAct as the cold outreach engine for /sales outreachCold outreach sequence generatorzubair-trabzada/ai-sales-team-claude · by zubair-trabzadaYou are the cold outreach engine for /sales outreach <prospect>. You generate complete, personalized, ready-to-send cold email sequences…★ 1.4k GitHub starsPromptAct as a B2B outbound sales expertAI-Powered B2B Cold Outreach Sequence Architecture & Multi-Channel Pipeline Generation Intelligence EngineAICMO/AiCMO-Marketing-Prompt-Collection · by AICMOYou are a B2B outbound sales expert.New listingSkillBuilds today's call listanthropics/knowledge-work-plugins · by anthropicsBuilds today's call list. Runs lead-triage to rank the top-5 leads most worth calling, supplies talking points from email history, blocks time on the calendar, and drafts follow-up messages. Trigger on "call list," "who am I calling today," "top five to call today," or "block time for calls." An owner who wants leads scored or ranked with no calendar blocks routes to lead-triage directly. Accepts optional count and date arguments.★ 25.5k GitHub starsSkillThe core CRE technique for increasing conversionsObjection/Counter-Objection (O/CO) Frameworkwondelai/skills · by wondelaiThe core CRE technique for increasing conversions. Don't guess objections—research them. Then systematically counter each one.★ 2.2k GitHub starsSkillYou generate strategic follow-up email sequencesFollow up sequence generatorzubair-trabzada/ai-sales-team-claude · by zubair-trabzadaYou generate strategic follow-up email sequences for prospects after initial contact has been made. This is NOT cold outreach — these are…★ 1.4k GitHub starsSkillYou generate comprehensive objection response scriptsObjection handling playbookzubair-trabzada/ai-sales-team-claude · by zubair-trabzadaYou generate comprehensive objection response scripts that salespeople can use in real-time during calls, meetings, and email exchanges.…★ 1.4k GitHub stars

More from mohitagw15856

SkillDesign a 360-degree feedback survey or write a structured360-Degree Feedback Template Skillmohitagw15856/pm-claude-skills · by mohitagw15856Design a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.★ 1.4k GitHub starsSkillDesign statistically rigorous A/B tests for product featuresA/B Test Planner Skillmohitagw15856/pm-claude-skills · by mohitagw15856Design statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.★ 1.4k GitHub starsSkillGenerate a WCAG 2.2 accessibility audit checklistAccessibility Audit Skillmohitagw15856/pm-claude-skills · by mohitagw15856Generate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.★ 1.4k GitHub starsSkillBuild a structured account plan for any key customerAccount Plan Skillmohitagw15856/pm-claude-skills · by mohitagw15856Build a structured account plan for any key customer or target account. Use when asked to create an account plan, key account strategy, strategic account review, or territory plan. Produces a complete account plan with relationship map, growth opportunities, risks, and 90-day action plan.★ 1.4k GitHub starsSkillOptimize an article for Answer Engine Optimization so AIAEO Optimizer Skillmohitagw15856/pm-claude-skills · by mohitagw15856Optimize an article for Answer Engine Optimization (AEO) so AI engines like ChatGPT, Perplexity, and Claude can extract, quote, and cite it. Use when asked to AEO-optimize, make content AI-readable, improve AI citation chances, or adapt an article for answer engines. Produces an AEO-optimised rewrite with question headings, 50–80 word answer capsules, a paragraph-length audit, and flagged trust signals.★ 1.4k GitHub starsSkillConduct a structured ethical review of an AI or ML featureAI Ethics Review Skillmohitagw15856/pm-claude-skills · by mohitagw15856Conduct a structured ethical review of an AI or ML feature, model, or product. Use when preparing to deploy an AI system, assessing algorithmic risk, auditing a model for bias, or producing a responsible AI impact assessment. Produces a structured ethics review covering fairness, transparency, privacy, safety, accountability, and societal impact with a risk tier score, pre-deployment checklist, and prioritised mitigations.★ 1.4k GitHub stars