skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
victor-shulga/outbound-engine-skills67 installs

linkedin-sequence

Use when asked to write a LinkedIn outreach sequence, connection request messages, or LinkedIn follow-ups for a specific hypothesis

How do I install this agent skill?

npx skills add https://github.com/victor-shulga/outbound-engine-skills --skill linkedin-sequence
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    The skill helps write LinkedIn outreach messages by processing profile data and social signals. It presents a surface for indirect prompt injection because it incorporates untrusted external content from LinkedIn profiles and posts into its generated output. It also recommends several third-party tools for automation and data retrieval.

  • Socketpass

    No alerts

  • Snykwarn

    Risk: MEDIUM · 1 issue

What does this agent skill do?

LinkedIn Sequence

Write a LinkedIn-specific outreach sequence — connection request note + follow-up messages — tied to a signal and persona. Different rules than email.

Required tools

Install these before running the skill. None of them is strictly required, the skill also runs on pasted input, but without them the result gets noticeably worse: the connection note and follow-up 2 lean on the persona in general because nobody read this person's profile or recent posts.

ToolUsed forRequired?Without it
Apify (LinkedIn profile and posts actors)read the person's role, tenure and recent posts for the note and for the new angle in follow-up 2Recommendedfollow-up 2 cannot reference what they posted; you paste the profile by hand
Firecrawl (MCP)read the company site, job posting or news item behind the signalRecommendedthe signal line is written from your summary and may miss the exact detail
HeyReach (MCP)load the note and follow-ups as a campaign and check limitsRecommendedyou copy the messages into the tool by hand

Alternatives: Sales Navigator can stand in for Apify; Exa can stand in for Firecrawl; Expandi or Aimfox can stand in for HeyReach.

Inputs to have ready:

  • ICP and persona (role, company type)
  • Signal the outreach is built around
  • Hypothesis and angle
  • Number of steps (default: connection request + 2 follow-ups)

LinkedIn-specific rules

Connection request note (300 character limit)

  • Must fit in 300 characters including spaces
  • No pitch in the connection request — the goal is to get accepted, not to sell
  • One sentence referencing why you're connecting + one light hook
  • No "I came across your profile" — too common
  • Reference their company or a specific signal if possible

Follow-up message 1 (sent after connection accepted)

  • Lead with the signal — what you noticed, not who you are
  • One sentence on what it implies
  • Soft CTA: a question, not a demo ask
  • Under 150 words

Follow-up message 2 (sent 3–5 days after message 1 if no reply)

  • Don't just "follow up" — add a new angle or piece of information
  • Can reference something they posted, shared, or commented on
  • One line ask at the end
  • Under 100 words

Process

  1. Confirm ICP, signal, angle, and persona are clear
  2. Draft connection request note (check: under 300 chars, no pitch)
  3. Draft follow-up 1: signal-led, specific, one question CTA
  4. Draft follow-up 2: new angle or social proof, one-line close
  5. Check all three against LinkedIn rules (no URLs in connection note, no spam language)

Terms and plain-language output

<!-- glossary:start terms=connection-request,follow-up,accept-rate,buying-signal,hypothesis,cta mode=copy -->

Rules for every text a reader will see (post, email, message, page copy):

  1. No internal codes or letter scales (A/B/C, D L T E, scores without words, framework codes). Write the meaning.
  2. Use the plain form from the table below. English stays only for tool names and for copy that ships in English. A term the reader may not know gets explained in the same sentence or replaced.
  3. Any review, audit or report this skill produces for the team or the client follows the document rules: open it with «Словник цього документа» (terms used, at most 10), do not score what depends on unfinished work, and open each section with one concrete action.
Internal term (this skill)Write for the readerWhat it means
connection request, CR, connection noteзапит на контакт у LinkedInЗапрошення з запискою до 300 символів; у ньому нічого не продаємо, мета лише щоб прийняли.
follow-up, FU1 / FU2наступне повідомленняПовідомлення після запиту на контакт чи першого листа; кожне додає нову думку замість «просто нагадую».
accepted connection rateчастка прийнятих запитів у LinkedInскільки людей із тих, кому надіслали запит у контакти, його прийняли.
buying signalознака готовності купуватифакт про компанію, після якого розмова про вашу послугу доречна саме зараз.
hypothesisгіпотеза (кому, на яку подію, з якою пропозицією)Одне припущення, яке перевіряє кампанія; результати рахуємо окремо по кожній гіпотезі.
CTAпрохання в кінці листаконкретний маленький наступний крок: відповісти, подивитися, погодитися на дзвінок
<!-- glossary:end -->

Output format

LinkedIn sequence: [hypothesis name]
Persona: [role] @ [company type]
Signal: [what triggered this]

CONNECTION REQUEST NOTE ([n] chars / 300)
---
[message]
---

FOLLOW-UP 1 — After connection accepted
---
[message]
---

FOLLOW-UP 2 — Day 3–5 if no reply
---
[message]
---

Notes

  • LinkedIn CTAs should be softer than email CTAs — "would this be relevant to you?" beats "want to jump on a call?"
  • If running both email and LinkedIn for the same hypothesis, stagger the channels — don't send both on day 1
  • Profile strength matters: before running LinkedIn at scale, run a LinkedIn profile audit first
  • Acceptance rate for connection requests below 30% = the note needs work or the targeting is off
  • Never paste the same message LinkedIn sends by default ("I'd like to add you to my network") — always write a custom note

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/victor-shulga/outbound-engine-skills/linkedin-sequence">View linkedin-sequence on skillZs</a>