Install
$ agentstack add skill-mfwarren-entrepreneur-claude-skills-objection-handling ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Objection Handling
Sales objection scripts, FAQ generation, and trust-building content for common buying hesitations.
Purpose
Every product faces the same core objections: price, timing, trust, need, and authority. This skill maps your specific objections and creates scripts to address each one honestly.
Workflow
Step 1: Gather Context
- Product/service and price point
- Sales channel (calls, chat, email, self-serve)
- Most common objections heard (if known)
- Ideal customer profile
Step 2: Map the Objection Categories
- Price: "It's too expensive" / "I can't afford it"
- Timing: "Not right now" / "Maybe later"
- Trust: "How do I know this works?" / "I've been burned before"
- Need: "I don't think I need this" / "We're fine without it"
- Authority: "I need to check with my partner/boss"
- Competition: "How are you different from X?"
Step 3: Create Response Scripts
For each objection:
- Acknowledge — Validate the concern (never dismiss it)
- Clarify — Ask a question to understand the real objection
- Reframe — Shift the perspective
- Proof — Provide evidence (testimonial, case study, guarantee)
- Close — Re-present the offer with the objection addressed
Step 4: FAQ Page Content
Turn top objections into FAQ entries for the website/sales page. Proactively address concerns before they arise.
Step 5: Trust-Building Content
Suggest content pieces that preemptively handle objections:
- Case studies for trust
- Comparison pages for competition
- ROI calculators for price
- Free trials/samples for need
Output Format
## Objection Handling: [Product]
### Objection Map
| Objection | Category | Frequency | Response Script |
|-----------|----------|-----------|----------------|
| "Too expensive" | Price | High | [Script] |
### Response Scripts
#### "It's too expensive"
**Acknowledge:** ...
**Clarify:** ...
**Reframe:** ...
**Proof:** ...
**Close:** ...
### FAQ Content
[Ready-to-publish FAQ entries]
### Trust Content Recommendations
[Suggested content pieces]
Constraints
- Never teach manipulation tactics — honest selling only
- Scripts should feel conversational, not rehearsed
- Always respect "no" — provide one reframe, then move on
- Don't create pressure tactics or false scarcity
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: mfwarren
- Source: mfwarren/entrepreneur-claude-skills
- License: MIT
- Homepage: https://mattwarren.co
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.