agentleFS
cwhited26cwhited26/pocket-agent-starter-skills/skills/sales/discovery-call-note-capture/SKILL.md

discovery-call-note-capture

Skill0 starsChanged 4 months agoMITView on GitHub

Log the few things from a discovery call that change the deal — pain, budget signals, decision process, exact words — and skip the transcript. After a sales or discovery call, when turning a messy conversation into notes the owner and the next draft can use.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    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:

    Don't: Write a paragraph that recaps the whole call chronologically — "We started by introducing ourselves, then she told me about her …

    line 30

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “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

Capture What Matters From a Call

A discovery call has five useful minutes buried in thirty. Capture the parts that move the deal — what hurts, who decides, what they can spend, the exact phrases they used — and let the rest go.

The technique

  • Log the pain in their words. The exact phrase they used ("I'm drowning in paperwork") is gold for the follow-up — quote it back later.
  • Log the decision process: who else signs off, what has to happen before they can say yes, when they need it.
  • Log budget signals — a number, a range, a flinch, a "we spent X on the last guy."
  • Log the one thing they care about most. Every deal has a center of gravity; name it.
  • Skip the play-by-play. Nobody needs "then we talked about the weather." Notes are for what changes the next move.

Do this, not that

Do: "Pain: 'losing two days a week to invoicing.' Decision: she decides, but her partner Dave has to bless anything over $5k. Budget: paid $6k for a system that didn't work. Cares most about: not having to retrain staff. Wants it live by August."

Don't: Write a paragraph that recaps the whole call chronologically — "We started by introducing ourselves, then she told me about her business history…" — burying the three facts that actually decide the deal.

Why this works

Notes you can act on beat notes that are complete. A transcript of the whole call is a haystack; the owner needs the needles — the pain, the decision-maker, the budget, the one thing they care about. Capturing the exact words matters because quoting a prospect back to themselves in the follow-up proves you listened, and that's often what closes.

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.