Skip to content
Back to skills

Call Prep

ASecurity

Build a 15-minute pre-call brief for a sales meeting -- company research, attendee intel, tailored discovery questions, and the objections likely coming with answers ready. Use before any prospect or customer call.

  • 2 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 6, 2026
ai-agentsgo

Security analysis

A100/100

Scanned September 6, 2026

npx -y skills add OneWave-AI/open-agent-stack --skill call-prep --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Call Prep?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Call Prep
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/onewave-ai-call-prep/badge)](https://www.skillsdirectory.com/skills/onewave-ai-call-prep)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: call-prep
description: Build a 15-minute pre-call brief for a sales meeting -- company research, attendee intel, tailored discovery questions, and the objections likely coming with answers ready. Use before any prospect or customer call.
---

# Call Prep

Walk in knowing more than the other side expects. Input: company name and meeting context (first call, demo, negotiation, renewal); attendee names/LinkedIn URLs if known; anything from the CRM or email thread history available.

## Workflow

1. **Research the company.** Web-search recent news, funding, leadership changes, hiring signals (what roles they are posting reveals priorities), and their own positioning language. Find the thing that changed recently -- meetings exist because something changed.
2. **Read the attendees.** Role, tenure, likely care-abouts by function (a CFO hears risk and payback; an ops lead hears hours saved). Note shared ground if it is real; skip manufactured rapport.
3. **Pull the history.** From CRM/email/notes provided: every prior touch, what was promised, open threads, and anything they told us before -- asking a question they already answered costs credibility.
4. **Write the brief**, one page: why this meeting is happening (their trigger, not our pipeline stage), 5-7 discovery questions sequenced from situation to pain to stakes -- specific to their business, not a generic SPIN list; the 3 objections most likely for this profile, each with an honest answer; the single realistic goal for the call and the specific next step to propose before hanging up.

## Rules

- Every discovery question must be un-Googleable -- if the answer is on their website, asking it burns the meeting.
- Objection answers are honest, including "that's a real limitation, here's the trade" where true.
- One goal per call. A brief with four goals produces a call with none.
- Flag what you could not verify; a brief with a wrong fact is worse than a gap.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…