Linkedin Reply Triager
Classify every inbound LinkedIn reply and route it to the right next move. Use when replies land in the inbox and you need to decide who is hot, who needs nurture, and who to drop.
Install
$ agentstack add skill-styfinity-linkedin-engine-linkedin-reply-triager ✓ 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-reply-triager) 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 Reply Triager
The inbox sorter. Replies are not equal. This skill reads each one, names what bucket it belongs in, and hands it to the right next skill so nothing rots and nothing gets a sales pitch it did not ask for.
Inputs
- One reply or a batch of replies, pasted in (include who said what if it is a thread): $ARGUMENTS
- The brief (persona, offer, pains) loads automatically.
Do this
For each reply, in order:
- Read the actual words, not the timing. A reply that came in slow can still be HOT; a fast one can be a brush-off.
- Classify into exactly one bucket: HOT, WARM, COLD, OBJECTION, WRONG-PERSON, or HOSTILE.
- Name the tell. Quote the one phrase or signal that put it in that bucket. One line.
- Route it:
- HOT (buying signal, asking how it works, wants a call) to /linkedin-sell-by-chat, or /linkedin-booking-closer if they are ready for a time.
- WARM (interested but not now, soft yes, "keep me posted") to /linkedin-followup-adapter.
- COLD (one-word, flat, polite-but-dead) to /linkedin-cold-reviver.
- OBJECTION (price, timing, trust, "already have someone") to /linkedin-objection-handler.
- WRONG-PERSON (not their call, not their remit) ask for the right contact, warmly.
- HOSTILE (annoyed, "stop messaging me") stop the sequence, no further outreach.
- Write a one-line suggested next message in the operator's voice.
Output
Per reply: the class, the tell (quoted), the route (the slash-skill or the action), and a one-line suggested next message. Label each clearly. Batch input gets one block per reply.
Rules
- Route every reply. No reply is left unclassified.
- Read the words, not a timer. The bucket comes from what they said.
- Nothing sends here. This skill only sorts and suggests; the routed skill drafts, the operator approves.
- No em-dashes. Use a comma, a period, or " - ".
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.