Install
$ agentstack add skill-styfinity-linkedin-engine-linkedin-sell-by-chat ✓ 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
LinkedIn Sell By Chat
The hero outreach skill. Selling on LinkedIn is a six-stage conversation, not a pitch. This skill reads where the thread actually is and drafts only the next message, so you never run ahead of the buyer.
Inputs
- The conversation so far, pasted in full, plus the offer: $ARGUMENTS
- The brief (offer, pains, voice profile) loads automatically.
Do this
- Read the thread and identify which of the six stages it is at right now. The six stages:
- Open on their world, not your offer. A genuine, specific opener about them.
- One real insight that earns the reply. Useful on its own, no ask attached.
- Qualify the problem, message one: confirm the problem actually exists for them.
- Qualify the problem, message two: confirm the problem actually hurts.
- Introduce the offer, ONLY after they have confirmed the problem exists.
- Send the calendar link, ONLY after they say yes to a call.
- Draft only the next single message for the stage they are at. One message, not a sequence.
- Never skip a stage. Never pitch before the problem is confirmed (stages 3 and 4). Never send the link before a clear yes (stage 6).
- If the thread is ambiguous, name the most likely stage, say why, and draft for that one.
Output
- The next message, ready to copy.
- The stage it belongs to (1 to 6).
- What a yes vs a no looks like at this stage, so the user knows whether to advance or hold.
Rules
- One message at a time. Never draft ahead of the buyer.
- Gate the offer behind problem-confirmation, and the link behind an explicit yes.
- Once they say yes, stop selling and book. Hand to /linkedin-booking-closer.
- Run /linkedin-humanizer on the draft if it reads stiff.
- Draft only. Claude drafts, the operator approves and sends. Sending happens only through the connected CLI/MCP layer, wired to your own LinkedIn session or provider key, hard-capped at 20 actions per day for new accounts.
- No em-dashes. No guaranteed-result or "10x in a week" promises.
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.