discovery-calls
Skill8 starsChanged 3 months agoMITView on GitHub
Run discovery calls that close deals. Use when the user has a call booked with a prospect and needs to prepare, or wants to improve their close rate. Also use when the user mentions "discovery call," "sales call," "client call," "how to close," "call prep," "pricing conversation," or "they want to get on a call." The goal of a discovery call is to understand the problem deeply, show relevant proof, propose a clear scope, and close. For getting to the call, see cold-dm and follow-up-sequences.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- vijaysuperpositionist/skillstheir own version, first seen Nov 1, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- vijaysuperpositionist/skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository23 other files it gives its agents.
- AGENTS.mdAGENTS.md
- cold-dmSkill
- content-sellingSkill
- follow-up-sequencesSkill
- keyword-searchSkill
- profile-optimizationSkill
- prospecting-listsSkill
- context-engineeringSkill
- design-docSkill
- discussSkill
- grillingSkill
- llm-wikiSkill
- opencode-sessionsSkill
- playwright-cliSkill
- pr-descriptionSkill
- demand-first-validationSkill
- founder-market-fitSkill
- idea-scoringSkill
- market-entry-strategiesSkill
- ship-v1Skill
- trend-researchSkill
- tiger-style-codingSkill
- voicenotesSkill
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
- Distinctive: line 36
Before every call: research the prospect (LinkedIn, Twitter, company website, recent posts), have 2-3 relevant case studies ready, know …
≈ “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
Discovery Calls
You are an expert at running discovery calls that convert prospects into paying clients. Your goal is to help the user prepare for and execute calls that close — without being pushy or salesy.
The Discovery Call Framework
Phase 1: Understand Their Problem (60% of call time)
Ask questions, listen, don't pitch yet: "Tell me about [project] — what are you working on?", "What's the biggest challenge you're facing with [area]?", "What have you tried so far?", "What happens if this doesn't get solved in [timeframe]?", "Who else is involved in the decision?", "Do you have a budget range in mind?"
The goal: understand the problem well enough to propose a specific solution. If you can describe their problem better than they can, you've earned their trust.
Phase 2: Show Relevant Proof (20% of call time)
Once you understand the problem, show them you've solved similar ones. Share screen with a relevant portfolio piece or case study — keep it specific to their problem, don't show your entire portfolio. Use numbers: "We shipped their API layer in 3 weeks" beats "We're really experienced."
Phase 3: Propose Scope + Price (15% of call time)
Be direct about what you'd do and what it costs: propose a clear scope (what's included, what's not), give a price range or fixed price, explain the timeline.
Pricing rules: quote fixed price for defined scope, day rate for open-ended work. Never quote below your floor (know it before the call). If they flinch, reduce scope, not price.
Phase 4: Close or Next Step (5% of call time)
"Does this sound like what you need?" / "What would you need to move forward?" / "I can send a proposal by [date] — does that work?" If they need time: "When would be a good time to follow up?"
Call Prep Checklist
Before every call: research the prospect (LinkedIn, Twitter, company website, recent posts), have 2-3 relevant case studies ready, know your pricing for likely scope, know your calendar availability, and have a proposal template ready to customise.
Common Mistakes
Pitching too early (talking about yourself before understanding their problem); not asking about budget (awkward silence beats wasting 2 hours on a prospect who can't pay); saying "I'll send a proposal" and not doing it for a week (send within 24 hours); ending a call with no clear next step; discounting before being asked.
When to Walk Away
Budget is below your floor and they can't flex, scope keeps expanding without budget increasing, they want free "prove yourself" work with no path to paid, or there are red flags (disrespectful communication, unrealistic expectations, no decision-maker on the call). Walking away from bad-fit clients protects your time for good-fit ones.
After the Call
Send a follow-up email within 2 hours summarising what you discussed, then a proposal within 24 hours (not 5 days). If they don't respond to the proposal, follow up in 3 days (see follow-up-sequences). After closing, schedule a check-in for 1 week out.
Related Skills
- cold-dm — get the call booked in the first place
- follow-up-sequences — follow up on proposals and post-call silence
- prospecting-lists — build a pipeline of prospects for future calls
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.

