Objection handling
Prepare honest, effective responses to common buyer/seller objections (commission, "we'll wait," overpricing, "why hasn't it sold," FSBO). Use when prepping for an appointment or a tough conversation.From its SKILL.md
npx -y skills add m-binimran/real-estate-pack --skill objection-handlingAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.5 KB, 306 tokens by cl100k_base, as published. Nobody here has run it
objection-handling
Acknowledge, understand, respond with value and facts - never with pressure or misrepresentation.
Framework (per objection)
- Acknowledge the concern genuinely.
- Clarify the real issue behind it (ask, don't assume).
- Respond with evidence - data, process, your value - not hype.
- Confirm it's addressed and move forward.
Common ones
- "Your commission is too high." Explain what's included (marketing, negotiation, coordination, net result), show value; commissions are negotiable - be straight about that.
- "We'll wait for the market." Share objective market data (the
market-report), not fear. - "Zillow says it's worth more." Walk through the
cmawith real comps; AVMs aren't appraisals. - "Why hasn't it sold?" Price, condition, exposure - honest diagnosis + a plan.
- FSBO / "we'll sell it ourselves." Show the gaps you fill; respect their choice.
Output
- Scripts per objection: acknowledge -> clarify -> evidence-based response -> next step. Keep them honest and brief.
Guardrails
- No pressure tactics, no false scarcity ("won't last"), no overpromises (the
superlativerule). - Commission talk: never imply rates are fixed or set by anyone but the brokerage/agreement.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.