Linkedin Objection Handler
Read pushback from a prospect and write an answer-first reframe that addresses the real concern and advances toward a call. Use when a reply contains an objection (price, timing, trust, fit, "we already do this").
Install
$ agentstack add skill-styfinity-linkedin-engine-linkedin-objection-handler ✓ 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.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-styfinity-linkedin-engine-linkedin-objection-handler) 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
LinkedIn Objection Handler
An objection is a question wearing a no. This skill answers it directly, reframes to the cost of staying still, and moves the thread one step toward a call.
Inputs
- The objection as the prospect wrote it, plus your honest answer to it: $ARGUMENTS
- The brief (offer, pains, proof, voice profile) loads automatically.
Do this
- Name the real concern underneath the words. Most objections are one of five: price, timing, trust, fit, or "we already do this". Say which one this is and why.
- Answer it first and directly. No dodging, no pivot before the answer lands. Use the operator's honest answer from the input as the spine.
- Reframe to the cost of the status quo. What does doing nothing keep costing them, in their own metric (leads, pipeline, hours, missed revenue)?
- Advance to a call. Offer a small, specific next step (a short call, a look at their numbers). Keep it conditional and low-pressure.
- Match the tone to the thread's warmth: cold gets shorter and lighter, warm can carry more substance.
Output
The reframe message, ready to paste, tier-matched to the thread's warmth. Then a one-line note stating the concern you actually addressed (price / timing / trust / fit / already-do-this).
Rules
- Answer-first, always. Never evade the objection or change the subject before it is handled.
- Never discount to win. Price objections get reframed against the cost of the status quo, not knocked down.
- Advance to a call, do not hard-close in the text. Sending happens later, through the connected CLI/MCP layer, capped at 20 actions/day for new accounts.
- Draft only. Claude drafts, the operator approves, and only then sends.
- No em-dashes. Reads like a peer who respects the prospect's pushback.
- If the reply has run hot and is ready to book, hand it to /linkedin-reply-triager. Run /linkedin-humanizer on the draft before sending.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: styfinity
- Source: styfinity/linkedin-engine
- License: MIT
- Homepage: https://styfinity.com
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.