meeting-prep-five-minutes
Skill5 starsChanged 4 months agoMITView on GitHub
Produces a one-page brief before a sales call: who they are, what they likely care about, what to ask, and what would disqualify them. Use when a call is imminent and nobody has prepared, or when back-to-back meetings mean prep keeps getting skipped.
In this repository30 other files it gives its agents.
- AGENTS.mdAGENTS.md
- ad-to-landing-promise-matchSkill
- b2b-audience-signal-auditSkill
- cold-outbound-sequence-reviewSkill
- competitor-lead-angle-reviewSkill
- crm-lead-source-quality-auditSkill
- discovery-call-gap-analysisSkill
- disqualification-reason-minerSkill
- email-nurture-sequence-reviewSkill
- form-friction-finderSkill
- ghosted-after-the-demoSkill
- google-ads-lead-quality-auditSkill
- icp-reality-checkSkill
- landing-page-qualification-reviewSkill
- lead-magnet-offer-fitSkill
- lead-scoring-sanity-checkSkill
- lead-to-opportunity-drop-off-reviewSkill
- linkedin-ads-lead-quality-auditSkill
- meta-ads-lead-quality-auditSkill
- objection-cheat-sheetSkill
- pipeline-hygiene-auditSkill
- proposal-win-loss-reviewSkill
- sales-follow-up-speed-auditSkill
- scale-readiness-check-lead-genSkill
- sdr-handoff-brief-generatorSkill
- spam-folder-checkSkill
- weekly-b2b-lead-gen-readoutSkill
- what-to-say-to-this-companySkill
- won-deal-to-case-studySkill
- write-the-follow-upSkill
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 11 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈11
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
- Distinctive: line 35
Write the questions you cannot answer from research.
- Distinctive: line 37
Write the disqualifiers explicitly, then decide what a good outcome is.
- Distinctive: line 43
If the research contradicts what the CRM says about this account, flag the contradiction rather than smoothing it over.
- Distinctive: line 44
If this is a follow-up call, the previous conversation outranks anything found online.
- Distinctive: line 45
If nothing meaningful can be found, say so and lean the brief entirely on questions.
- Distinctive: line 49
Keep the whole thing to one screen.
- Distinctive: line 91
Do not compile personal information beyond what is professionally relevant to the meeting.
- Distinctive: line 92
Do not invent facts about the company or the attendees.
- Distinctive: line 93
Do not write a script. The output is a brief, and a call read from a script sounds like one.
- Distinctive: line 94
Do not skip the disqualifiers, even when the deal is wanted.
- Distinctive: line 95
Do not treat a LinkedIn headline as a job description.
≈ “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.
Files
Meeting Prep in Five Minutes
Use this skill when
There is a call soon and nobody has read anything about the company.
You have twenty minutes before a call. The goal is to walk in knowing three things you did not know, rather than forty you will not remember.
The output is deliberately short. A brief nobody reads before the call is worth less than no brief, because it also consumed the prep time.
Required input
- Company name and website.
- Who is on the call, and their roles.
- Whether this is a first call, a follow-up, or a late-stage conversation. The brief is different for each.
- What you sell.
Useful if it exists, skipped without complaint if not:
- previous emails or notes with this account
- how they arrived: inbound, outbound, referral, event
- which competitor they are likely using
- your typical deal size and the size this one looks like
Analysis workflow
- Establish the basics fast: what they sell, roughly how big, who they sell to. Two minutes, not twenty.
- Work out who is actually in the room. A founder, a head of department and a procurement lead each want a different conversation, and preparing for the wrong one is worse than preparing for none.
- Find at most three specifics worth mentioning. More than three will not survive the first five minutes of an actual conversation.
- Write the questions you cannot answer from research. The point of the call is what the website does not say, so a brief that answers everything has prepared the wrong things.
- Name the likely objection for this profile, and the honest response to it.
- Write the disqualifiers explicitly, then decide what a good outcome is. Not "a great conversation", a specific next step.
Decision rules
- Three facts maximum. This is a hard limit, not a guideline.
- Questions beat statements in the brief. If the brief is mostly things to say, it is a pitch script and the call will feel like one.
- If the research contradicts what the CRM says about this account, flag the contradiction rather than smoothing it over.
- If this is a follow-up call, the previous conversation outranks anything found online.
- If nothing meaningful can be found, say so and lean the brief entirely on questions. That is a normal outcome for small and private companies.
Output format
Keep the whole thing to one screen.
Who they are
Two lines. What they sell, roughly how big.
Who is on the call
Name, role, and what someone in that role usually cares about here.
Three things worth knowing
Bullets. Each with its source.
Ask these
Four to six questions, ordered, the sharpest first in case the call runs short.
Likely objection
The one you will probably hear from this profile, and the honest answer.
Disqualify if
The two or three signals that mean this is not a fit, so it can be said out loud on the call rather than discovered in month three.
A good outcome looks like
One specific next step.
Practical example
A first call with a fifty-person recruitment agency, booked from a cold email, attended by the operations director.
The brief notes that the agency runs contract placements rather than permanent, which changes the entire billing conversation; that they have four offices, which suggests a coordination problem; and that they mention a specific applicant tracking system on their site.
The questions target how contract billing works today and where the manual work sits. The likely objection is that they already have the tracking system, and the honest answer separates what that system does from what it does not.
The disqualifier is written down before the call: under twenty placements a month means the manual work is not painful enough yet, and the right move then is to say so and set a reminder rather than push.
Guardrails
- Do not compile personal information beyond what is professionally relevant to the meeting.
- Do not invent facts about the company or the attendees. An empty section is better than a confident guess.
- Do not write a script. The output is a brief, and a call read from a script sounds like one.
- Do not skip the disqualifiers, even when the deal is wanted.
- Do not treat a LinkedIn headline as a job description. It states aspiration as often as reality.
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
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.

