agentsclimarketplace
Sign in

Call prep

Skill OneWave-AI/open-agent-stack/plugins/sales-desk/skills/call-prep

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.From its SKILL.md

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

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.9 KB, 362 tokens by cl100k_base, as published. Nobody here has run it

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.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most sales audience skills give in 362 tokens

Counted across 401 of the 401 authors here whose files we hold, read 2026-08-07

  • Read product marketing context before asking questionsin 21 of 401, across 11 files
  • Acknowledge competitor strengths honestlyin 18 of 401, across 7 files
  • Start every page with a summaryin 15 of 401, across 4 files
  • Use a single, low-friction call to actionin 15 of 401, across 7 files
  • Create a single source of truth for each competitorin 14 of 401, across 3 files
  • Make each follow-up email add new valuein 11 of 401, across 5 files
  • Cut any sentence that does not drive a replyin 10 of 401, across 4 files
  • Tie personalization directly to the problemin 10 of 401, across 4 files
  • Write paragraph comparisons for each dimensionin 9 of 401, across 3 files
  • Link between related competitor pagesin 9 of 401, across 3 files
  • Keep subject lines short and lowercasein 9 of 401, across 3 files
  • Define ideal customer profile from top customersin 9 of 401, across 3 files

Said here and by no other author read

  • read attendees by role and likely priorities
  • pull all prior touchpoints from provided history
  • write five to seven discovery questions
  • sequence questions from situation to pain to stakes
  • answer three likely objections honestly
  • define one realistic goal for the call

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.