agentleFS
prosyo-aiprosyo-ai/gtm-skill/skills/cold-call-script/SKILL.md

cold-call-script

Skill13 starsChanged 21 days agoMITView on GitHub

Use this skill when you need a B2B cold call script or talk track: \"write a cold call script\", \"what do I say when they pick up\", \"help me prep cold calls for this list\", \"handle objections on the phone\". Builds an opener that earns 30 seconds, a problem statement in the buyer's words, two or three discovery questions, a meeting ask and the responses to the most common brush-offs. Written to be said out loud, with a one-page version for the call and a practice drill.

4 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

9 rules. 0 are common, 9 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 9

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this before a calling block.

    line 16
  2. Distinctive:

    Ask, listen, follow the answer.

    line 39
  3. Distinctive:

    If there is a problem: "Contoso was at 9 days and now closes in 4.

    line 42
  4. Distinctive:

    If there is no problem: thank them, ask who else might feel it, and leave.

    line 43
  5. Distinctive:

    Read references/call-objections.md for responses to the ten most common brush-offs.

    line 46
  6. Distinctive:

    MUST say who you are and that it is a sales call when asked.

    line 67
  7. Distinctive:

    MUST respect do-not-call lists and local calling rules and hours.

    line 68
  8. Distinctive:

    NEVER pretend to know the prospect or reference a conversation that did not happen.

    line 69
  9. Distinctive:

    NEVER keep pushing after a clear no.

    line 70

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Use this before a calling block. It produces a talk track that sounds like a person, not a reading, and that gets to a decision (meeting or no) in under three minutes.

Inputs

  • Persona and the problem.
  • Offer and one strong proof point.
  • Trigger or prior touch (an email they may have seen).

The play

1. Opener: honest and short

Name yourself, acknowledge the interruption, give the reason in one sentence, ask for 30 seconds.

"Hi Maya, it's Sam from Acme. This is a cold call, so feel free to hang up, but can I tell you why I called and you decide if it's worth a minute?"

Permission-based openers convert better than pretending the call is expected.

2. Problem statement: the reason

One or two sentences about a problem people in their role usually have, with a peer reference. End with a question.

"I work with finance leads at companies your size. Most tell me close takes 8 to 10 days because approvals sit in inboxes the last week of the month. Is that true for you, or have you solved it?"

3. Discovery: two or three questions

Ask, listen, follow the answer. Good questions are about their current process and its cost: "How long does close take today?", "Where does it get stuck?", "What happens when it runs late?"

4. The ask

If there is a problem: "Contoso was at 9 days and now closes in 4. Worth 20 minutes next week to see if the same thing would work for you? Tuesday or Thursday?" If there is no problem: thank them, ask who else might feel it, and leave.

5. Brush-offs

Read references/call-objections.md for responses to the ten most common brush-offs. The principle: acknowledge, ask one question, then respect the answer.

One-page call card

Opener: <permission line>
Reason: <problem + peer>  →  "Is that true for you?"
Questions: 1. <current process>  2. <where it breaks>  3. <cost of it>
Proof: <one line>
Ask: <20 minutes, two time options>
If no: "Who else on your team deals with <problem>?"

What good looks like

  • The rep speaks less than 50% of the call.
  • A clear outcome every time: meeting, referral, follow-up date, or a no.
  • The common mistake is the pitch dump: 90 seconds of features before the prospect has said a word.

Rules

  • MUST say who you are and that it is a sales call when asked.
  • MUST respect do-not-call lists and local calling rules and hours.
  • NEVER pretend to know the prospect or reference a conversation that did not happen.
  • NEVER keep pushing after a clear no.

Example prompts

  • "Write a cold call script for IT directors at hospitals. We sell device management."
  • "Prep me for 40 calls tomorrow to people who were sent our email last week."
  • "Give me responses to 'just send me an email' and 'we're all set'."

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.