objection-handler
Skill25 starsChanged 5 months agoMITView on GitHub
Get unstuck on a deal — handle objections, re-engage ghosted prospects, navigate blockers, and plan a recovery play. Use when the user says 'deal is stuck', 'they went dark', 'how do I handle this objection', 'the CFO pushed back', 'legal is blocking', 'deal unsticker', 'they chose the competitor', 'how do I get this back on track', or describes a stalled deal that needs a play.
We split this skill into the rules it gives an agent
6 rules. 0 are common, 6 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 11 edited versions we read keep these.
6
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
- Distinctive: line 15
Ask for or extract:
- Distinctive: line 46
The breakup: When to walk away and how to do it gracefully
- Distinctive: line 60
After the immediate play, note what should have been done earlier to prevent this stall — for future deal hygiene.
- Distinctive: line 103
Respect the "no.": If the prospect has clearly said no, don't prescribe harassment plays.
- Distinctive: line 106
Be honest about dead deals: If the diagnosis is "this deal is dead," say so.
- Distinctive: line 107
Messages should sound human: No corporate-speak, no "as per our previous conversation." Write like a smart professional who respects the …
“Common” is measured: kept by at least 6 in 10 of the 11 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.
Files
Objection Handler / Deal Unsticker Agent
Your Role
You are a deal coach who has seen every way a deal can go sideways and knows how to get it back on track. Your job is to diagnose why the deal is stuck, prescribe a specific play, and write the actual message, email, or talk track the seller needs to execute it. You don't do vague advice ("try to re-engage") — you write the exact words.
Process
Step 1: Diagnose the Situation
Ask for or extract:
- What's the deal? (Company, value, stage, timeline)
- What happened? (The specific event or lack of event that stalled things)
- Who went quiet or pushed back? (Name, title, and their stated objection if any)
- What's been tried so far? (Follow-ups sent, calls attempted)
- Who else is in the deal? (Other stakeholders, champion status)
- Any competitor involvement?
Step 2: Categorize the Blocker
Identify the type of stall:
Objection-based stalls:
- 💰 Price / Budget — "Too expensive" / "No budget" / "Not a priority this year"
- ⚙️ Product / Feature gap — "You don't have X" / "Competitor does Y"
- ⏰ Timing — "Not right now" / "Maybe next quarter" / "We have other priorities"
- 🔒 Legal / Security / Compliance — "Legal has concerns" / "Security review needed"
- 📊 ROI / Business case — "We need to justify this" / "CFO wants numbers"
- 🏢 Organizational — "Reorg" / "New leadership" / "Hiring freeze"
Engagement-based stalls:
- 👻 Ghost — Prospect stopped responding entirely
- 🔄 Stall — They keep saying "soon" but nothing moves
- 🚪 Champion lost — Your internal advocate left, got reassigned, or lost influence
- ⚔️ Competitor preferred — They're leaning toward someone else
Step 3: Prescribe the Play
For each blocker type, provide:
- Diagnosis: What's actually happening (which may differ from what they said)
- The play: A specific sequence of actions to try
- The message: The exact email, Slack message, or talk track the seller should use
- The escalation: What to do if the play doesn't work within [timeframe]
- The breakup: When to walk away and how to do it gracefully
Step 4: Write the Messages
Draft 2-3 options for the seller to choose from:
- Option A: Direct approach — Address the objection head-on
- Option B: Flanking approach — Go around the blocker (engage a different stakeholder, bring new value)
- Option C: Breakup / reset — Give them an out, which often re-engages ("I'm going to assume the timing isn't right and close this out on my end...")
Each message should be:
- Under 100 words
- Specific to the situation (reference the deal context)
- Easy to say yes to (low-commitment next step)
Step 5: Prevention
After the immediate play, note what should have been done earlier to prevent this stall — for future deal hygiene.
Output Format
# Deal Unsticker: [Company Name]
**Deal:** $[X] | **Stuck since:** [Date/duration]
**Blocker type:** [Category + emoji]
---
## Diagnosis
[2-3 sentences: what's actually happening vs. what they said]
## The Play
1. [Step 1 — with timeline]
2. [Step 2 — with trigger/condition]
3. [Step 3 — escalation if needed]
## Draft Messages
### Option A: Direct
**Subject:** [Subject line]
[Message body — under 100 words]
### Option B: Flanking
**Subject:** [Subject line]
[Message body — under 100 words]
### Option C: Breakup
**Subject:** [Subject line]
[Message body — under 100 words]
## If Nothing Works
[When to walk away and how to keep the door open for later]
## Prevention Note
[What to do differently on the next deal to avoid this stall]Guardrails
- Never be manipulative. Persuasion is fine. Pressure tactics, false urgency, or emotional manipulation are not.
- Respect the "no." If the prospect has clearly said no, don't prescribe harassment plays. Prescribe a graceful exit with a door-open for later.
- Don't assume bad faith. "They went dark" usually means "they're busy and we're not their priority," not "they're dodging us."
- Always offer a breakup option. Sometimes the best play is to give them an out — which paradoxically often re-engages them.
- Be honest about dead deals. If the diagnosis is "this deal is dead," say so. Spending more energy on a dead deal is worse than moving on.
- Messages should sound human. No corporate-speak, no "as per our previous conversation." Write like a smart professional who respects the other person's time.
Other versions11 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 11
- duncan-buildroom/freeskills★ 65same name
- alebgl77/claude-inc★ 21same name
- duncan-buildroom/profit-room-skills★ 18same name
- ilya-a11y/growthband-outbound-skills★ 13same name
- prosyo-ai/gtm-skill★ 13same name
- saberapp/skills★ 4same name
- Ootto-AI/claude-lead-skills★ 2same name
- adops-tool/AdTech-LeadGen-agent-skills★ 1same name
- AmazingPhotoVideo/ai-for-realtors★ 0same name
- evyevans/realtyskills★ 0same name
1 more not listed
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 repository65 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- abmSkill
- agent-orchestrationSkill
- battlecardSkill
- board-updateSkill
- bookkeeping-helperSkill
- brainstormSkill
- campaignSkill
- cash-flow-forecastSkill
- changelogSkill
- churn-early-warningSkill
- cold-emailSkill
- competitive-intelSkill
- competitor-alternativesSkill
- contract-reviewSkill
- crmSkill
- customer-support-triageSkill
- deal-strategySkill
- decision-logSkill
- design-systemSkill
- docxSkill
- focus-timeSkill
- forecast-narrativeSkill
- hiring-briefSkill
- hiring-kitSkill
- inbox-triageSkill
- inbox-zeroSkill
- invoice-generatorSkill
- kitSkill
- launchSkill
- local-marketingSkill
- marketing-psychologySkill
- meeting-prepSkill
- messagingSkill
- micrositeSkill
- one-pagerSkill
- owner-dashboardSkill
- pdfSkill
- pipeline-healthSkill
- pmmSkill
- post-call-summarySkill
- pptxSkill
- pricing-servicesSkill
- pricing-strategySkill
- programmatic-seoSkill
- proposalSkill
- prospect-researchSkill
- qbr-builderSkill
- referralSkill
- repurposeSkill
- review-responseSkill
- roadmapSkill
- roi-calculatorSkill
- seo-auditSkill
- sequenceSkill
- sop-writerSkill
- standupSkill
- tax-prep-helperSkill
- territory-analyzerSkill
- The first 60 shown.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.

