composio-community/awesome-gtm-skills/discovery-call-prep

Claude Code and agent skill by composio-community/awesome-gtm-skills

Trust tier 3
  • community
Source check pending

Checking that the SKILL.md file is still in the repository.

Prep for a discovery call — research the account, the attendee, set hypothesis for their pains, write the question stack, define success. Use on "prep for my discovery call", "research this account before tomorrow", or "what should I ask <prospect>?".

Install

npx vskill@latest install composio-community/awesome-gtm-skills/discovery-call-prep

SKILL.md

Discovery Call Prep

A great discovery call is an earned conversation, not a generic script. Prep is where the edge comes from.

Workflow

  1. Inputs. Account, attendee(s) + titles, date/time, source of the meeting (inbound, outbound, referral), product fit hypothesis.
  2. Research (web + LinkedIn + any CRM notes):
  • Company: stage, funding, recent news, hiring, public pain signals
  • Attendee: tenure, prior companies, what they're measured on, public content
  • Peers already using us / competitors (reference ammo)
  1. Form 3 pain hypotheses ranked by likelihood. For each: the leading signal, the words they'd use to describe it, who else it affects.
  2. Write the prep doc to ./prep/<account>-<date>.md.

Prep doc template

# <Account> — Discovery — <date>
 
## Snapshot
- Stage/size/funding
- Recent signals (hires, launches, news)
- Why meeting now: <source + any context from prior touches>
 
## Attendee
- <Name> — <Title> — <tenure>
- What they likely care about: <metric/KPI>
- Prior-company pattern: <if relevant>
 
## Pain hypotheses (ranked)
1. <Pain> — signal: <X> — their words: "<probable phrasing>"
2. …
3. …
 
## Question stack
Opening: "Walk me through how you handle <workflow> today."
Going deeper:
- "What changed that put this on your plate?" (trigger)
- "Who else is affected when <current pain>?" (committee)
- "What's the cost of not solving this in <timeframe>?" (stakes)
- "What would have to be true for you to pick a solution this quarter?" (criteria)
Verification:
- "If I'm hearing you right — <paraphrase>. Is that fair?"
 
## Landmines (questions we don't want surfaced yet)
- Pricing before value is established
- <Competitor> comparison before pains are clear
 
## Desired next step
<Specific next meeting / output / access> by <date>.
 
## Reference ammo
- <Lookalike customer> — outcome — available for reference? Y/N
- <Case study link>

Guardrails

  • Don't write > 8 questions in the stack — you won't get through them, and it becomes interrogation.
  • Every hypothesis needs a signal, not just a guess. If you can't cite one, lower its rank.
  • If the account is < 25 employees and you're selling to 500+, flag the mismatch and consider re-qualifying the meeting.

Security

  • Security scanPassed, 90 of 100Pattern checks on the skill's files.
  • Model reviewPassed

See the full security report

Quality evaluation

  • Task evaluationNot runNo evaluation yet. Run one in Skill Studio.

See evaluation results

Source

Popularity

7-day trend score
5

Not refreshed yet.

Works with

Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.

  • Claude Code
  • Cursor
  • GitHub Copilot
  • Windsurf
  • Codex
  • Gemini CLI
  • Cline
  • Amp
  • Roo Code
  • Goose
  • Continue
  • Kilo Code
  • Junie
  • Trae
  • OpenHands
  • Qwen Code
  • AI Agent
  • Tabnine Chat
  • Sourcegraph Cody
  • Amazon Q
  • Firebase Genkit
  • Sweep
  • Devin
  • Phind
  • Mentat
  • Claude Desktop
  • Aider
  • GPT Pilot
  • Plandex
  • bolt.new
  • v0
  • Replit Agent
  • Anse
  • TypingMind
  • BetterChatGPT
  • LibreChat
  • Warp AI
  • Pieces
  • Fig AI
Embed badge
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/composio-community/awesome-gtm-skills/discovery-call-prep/badge)](https://verified-skill.com/skills/composio-community/awesome-gtm-skills/discovery-call-prep)

Something wrong with this skill or its page? Tell us.