Linkedin Followup Adapter
Write the next follow-up from where the conversation actually is, off the real state of the thread rather than a fixed timer. Use when a prospect has gone quiet and the next touch needs a new angle.
Install
$ agentstack add skill-styfinity-linkedin-engine-linkedin-followup-adapter ✓ 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.
About
LinkedIn Follow-up Adapter
A follow-up is a new move, not a reminder. This skill reads the real state of the conversation and writes the next message off THAT, adding a fresh piece of value every time.
Inputs
- The thread so far and what actually happened on the last touch (they replied and went quiet, they opened a loop, they raised an objection, they ghosted after a yes): $ARGUMENTS
- The brief (persona tone, pains, offer) loads automatically.
Do this
- Read where the conversation actually is. Name the real state in one line: warm-but-busy, half-objection, interest-without-action, or genuine silence. Write off that, not a calendar.
- Pick a new angle, different from the last touch. If the last message asked a question, this one gives. If the last gave value, this one references a signal or a result.
- Add one new piece of value: a relevant observation, a useful resource, a specific result a client or operator saw, a single sharp question. Never restate the prior ask.
- Write the message short and human. Reads like a peer continuing a real thread.
- If their reply signals heat, hand it to /linkedin-reply-triager instead of sending another nudge. Run /linkedin-humanizer on the draft before it ships.
Output
- The next message, labelled clearly.
- The angle it takes and the conversation state it answers, one line.
- When to send it, expressed relative to the last touch, not a fixed date.
Rules
- State-driven, never timer-driven. The thread tells you when and what, not the clock.
- New angle and new value on every touch. If you cannot add value, do not send.
- Banned phrase: "just following up" (and its cousins "bumping this", "circling back", "checking in").
- No em-dashes. No "hope you're well".
- Draft only. Claude drafts, the operator approves. Sending runs through the connected CLI/MCP layer on the operator's own session or provider key, shows the draft first, and is capped at 20 actions per day for new accounts.
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.