Linkedin engagement handler
Use this skill when monitoring comments and reactions on a team member's LinkedIn posts.
How to use it
Claude Code
- Run the line below. It pulls the whole folder into
~/.claude/skills/linkedin-engagement-handler. - Describe your job in plain words. Claude Code follows the skill from there.
npx degit swan-gtm/gtm-skills/skills/ariel-cohen/linkedin-engagement-handler#main ~/.claude/skills/linkedin-engagement-handlerFor one project only, change the path to .claude/skills/linkedin-engagement-handler.
Claude (web or desktop app)
- On this page open ⋯ → Download .md.
- Save it as SKILL.md in a folder, zip the folder, then Customize → Skills → + → Create skill → Upload a skill.
- Pick the file and Save. Claude shows the name and description and runs a security scan.
- Check the skill is switched on.
- Start a new chat and describe your job in plain words. The AI follows the skill from there.
ChatGPT or another app
- ChatGPT: make a Project and paste it into Instructions.
- Neither? Paste it at the top of a new chat — it works for that chat.
Not working?
- Check which app you pasted it into — the steps above name the right one.
- Some skills need the paid tier of Claude or ChatGPT.
Paste into Claude, ChatGPT or Cursor.
Source of Linkedin engagement handler
Show the full text191 lines
| name | title | description | category |
|---|---|---|---|
| linkedin-engagement-handler | Handle LinkedIn post engagement signal | Use this skill when monitoring comments and reactions on a team member's LinkedIn posts. Comments get the full treatment — ICP + persona gating, CRM and account-memory logging, lead scoring, and a high-value path to connection requests and Slack alerts — while lone reactions are logged as a light touch unless the account is top-tier or a repeat engager. Repeat engagers escalate to high intent after an active-buyer check, with a personalized multi-channel draft queued for review. | Signals |
Template placeholders
Replace every {{...}} before enabling. See the setup checklist reference for the full setup list.
{{PROFILE_OWNER}}— Team member whose LinkedIn posts are monitored{{INTERNAL_DOMAINS}}— Your company domain(s){{TEAM_MEMBERS}}— First names / known aliases of your team (engagement from them is ignored){{CRM}}— Your CRM (e.g. HubSpot){{ENGAGEMENT_CHANNEL}}— Slack channel for high-value engagement alerts{{CRM_HYGIENE_SKILL}}— Sub-skill reference: how to create/update companies & contacts in your CRM{{LEAD_SCORING_SKILL}}— Sub-skill reference: lead scoring & qualification methodology{{ALERT_FORMAT_SKILL}}— Sub-skill reference: your alert formatting skill (optional — inline the format if you don't have one){{HIGH_ACV_TAG}}— Workspace tag marking high-ACV-potential accounts{{SELF_SERVE_THRESHOLD}}— Company size below which accounts are self-serve (default: fewer than 30 employees){{ALERT_TIERS}}— Tiers that always alert on first touch (default: Gold, Diamond)
Signal type — read first
Check the event type in the webhook payload before processing:
- New comment → full treatment (everything below).
- New reaction (like) → light touch only: log to {{CRM}} + account memory, then stop. No connection request. No Slack alert. Exception: if the company is tagged {{ALERT_TIERS}}, or this is a repeated engagement (2+ interactions), apply the full treatment.
Comments and reactions are deliberately separate lanes: a comment is an opinion someone attached their name to; a lone like is awareness at best — volume is far higher and signal far lower.
Engagement Process
For Every ICP Lead/Agency Interaction
When someone from an ICP company or relevant agency comments on or likes {{PROFILE_OWNER}}'s post, AND they match a relevant persona:
Relevant personas (tune to your ICP's buying committee):
- Sales Leader (CRO, SVP Sales, VP Sales, Head of Sales, Director of Sales)
- Growth Lead (Head of Growth, Director of Growth, VP Growth, or senior marketing leader)
- CEO (for companies in your core geographic/vertical segment)
- Agency Owner (for agencies in your space)
- GTM Engineer (GTM Engineer, Revenue Engineer, Marketing Engineer, Sales Engineer focused on GTM infrastructure)
- RevOps Lead, Head of Demand Gen, CMO
Ignore engagement from:
- CFOs, finance roles
- CTOs, engineers, technical roles (unless they're also founders/CEOs or GTM-focused)
- HR, operations, customer success
- Individual contributors without buying responsibility (except the engineer-persona exception above)
- Your own team ({{INTERNAL_DOMAINS}} domain, or known names: {{TEAM_MEMBERS}})
- Universities, academic institutions, professors, researchers
- Companies below {{SELF_SERVE_THRESHOLD}} (self-serve)
If the person is from an ICP company but NOT a relevant persona, ignore the engagement entirely.
Standard Processing (All ICP + Relevant Persona Engagers)
- Check relationship status — Are they a customer, active pipeline, or closed-lost? If yes, acknowledge but don't run the standard engagement flow.
- Mark awareness stage — Update the company record to your Aware stage if they're not already further along in the funnel. Never move a company backwards.
- Update {{CRM}} + account memory — Log the engagement (who, what they said, which post) and update the account record. Follow {{CRM_HYGIENE_SKILL}} for CRM writes.
- Run Lead Scoring — After processing (only when the person belongs to an identifiable company), run {{LEAD_SCORING_SKILL}}. LinkedIn engagement is the lowest-weight signal — include it in the signal stack but do not let it alone push an account above the second-lowest tier.
High-Value Path (High ACV + Decision Maker Only)
After standard processing, check if the engager's company has the {{HIGH_ACV_TAG}} tag AND the engager is a strong buyer persona (CRO, VP Sales, VP Marketing, CMO, CEO, Co-founder, RevOps Lead, Head of Demand Gen, Agency Owner, or equivalent GTM leadership).
If BOTH conditions are met:
- Queue a LinkedIn connection request from {{PROFILE_OWNER}}'s account for approval. Connection requests carry no note by design (better acceptance rates). Skip if already connected. (⚠️ Policy decision — see the checklist. The original deployment auto-sent these with no approval for this narrow high-ACV + decision-maker path; switch to auto-send only as a conscious opt-in.)
- Post to {{ENGAGEMENT_CHANNEL}} with:
- Who engaged (name, title, company)
- What they said (comment text)
- Which post they commented on
- ACV tier and why they qualify for the high-value path
- A link to the engager's LinkedIn profile
If either condition is NOT met (not high ACV, or not a decision maker) — stop after standard processing. No connection request, no Slack post. The engagement is logged and scored silently.
Repeated Engagement (2+ Interactions)
When the same ICP lead engages 2 or more times across {{PROFILE_OWNER}}'s posts:
Active buyer check (run before any escalation): verify the engager is currently active in a buying role at the ICP company:
- Is the ICP company their primary, active role? If they have stepped back (currently running a separate startup, recently founded a new company, or no longer day-to-day there), treat them as a non-buyer and stop — do not surface, do not sequence, do not create a task.
- If their primary/active company is itself not an ICP fit (a 2-person startup, a personal venture studio, or self-serve territory), stop. Do not escalate on their nominal association with the larger company.
- Partner-potential exception: a GTM operator, agency owner, or advisor who might refer clients to you gets flagged to your partnerships owner instead of routed as a buyer.
If the active buyer check passes:
- Move to high intent — Update their stage to MQL (high intent signal)
- Build a multi-channel sequence — Create a personalized multi-channel
campaign, queued for review (never sent automatically):
- Open with a question tied to your product's core problem space
- Personalize based on their engagement history and what they do
- Use both LinkedIn and email if available
- Reference their repeated engagement naturally
- Post to {{ENGAGEMENT_CHANNEL}} flagging this as high-intent (2+ interactions), include the full engagement history, and recommend immediate follow-up. This notification fires regardless of ACV tier — repeated engagement is always worth surfacing.
- Load {{ALERT_FORMAT_SKILL}} for the alert format (or inline your format here).
First-touch alert-tier rule: Even on a first interaction, if the engager's company is tagged {{ALERT_TIERS}}, immediately post to {{ENGAGEMENT_CHANNEL}} with a high-priority flag. Do not wait for a second interaction.
Lead Magnet Posts
Some posts may offer a lead magnet (e.g., "Comment X to get Y"). When this happens:
- Current lead magnet: There is no active lead magnet at this time. Do NOT share any URLs or documents. Treat commenters on lead magnet posts with the standard processing flow.
- Future lead magnets — {{PROFILE_OWNER}} updates this section before each new lead magnet post with the post topic and corresponding URL. The skill only ever shares the URL written here — never an inferred or remembered one.
Key Principles
- Track ALL comments and reactions (likes) from ICP companies and agencies
- High-value path (connection request + Slack) only fires for high ACV + decision maker — don't burn {{PROFILE_OWNER}}'s connection budget on low-value targets
- Repeated engagement always gets surfaced, regardless of ACV tier
- Always personalize based on what they said
- If outreach is needed, build the campaign — don't just recommend reaching out
- Keep initial outreach warm and helpful, not salesy
- LinkedIn engagement is the lowest-weight signal — capped at the second-lowest tier unless stacked with other signals
What good looks like
A great run processes only engagers who clear both gates — ICP company and buying persona — and the high-value path fires precisely: high-ACV tag plus decision maker, nothing else. Repeat engagers get a personalized multi-channel draft queued for review with their full engagement history attached, and every alert includes what the person actually said.
Lone reactions stay in their light-touch lane, and repeat engagers who have stepped back from the ICP company get caught by the active-buyer check instead of escalated.
Mediocre looks like: full-treatment alerts fired on a lone like, connection requests burned on individual contributors, engagement alone driving Gold or Diamond tiers, alerts without the comment text, or sequences going out without review.
| 1 | |
| 2 | name "linkedin-engagement-handler" |
| 3 | title Handle LinkedIn post engagement signal |
| 4 | description "Use this skill when monitoring comments and reactions on a team member's LinkedIn posts. Comments get the full treatment — ICP + persona gating, CRM and account-memory logging, lead scoring, and a high-value path to connection requests and Slack alerts — while lone reactions are logged as a light touch unless the account is top-tier or a repeat engager. Repeat engagers escalate to high intent after an active-buyer check, with a personalized multi-channel draft queued for review." |
| 5 | category Signals |
| 6 | |
| 7 | |
| 8 | ## Template placeholders |
| 9 | |
| 10 | Replace every `{{...}}` before enabling. See the setup checklist reference for the full setup list. |
| 11 | |
| 12 | `{{PROFILE_OWNER}}` — Team member whose LinkedIn posts are monitored |
| 13 | `{{INTERNAL_DOMAINS}}` — Your company domain(s) |
| 14 | `{{TEAM_MEMBERS}}` — First names / known aliases of your team (engagement from them is ignored) |
| 15 | `{{CRM}}` — Your CRM (e.g. HubSpot) |
| 16 | `{{ENGAGEMENT_CHANNEL}}` — Slack channel for high-value engagement alerts |
| 17 | `{{CRM_HYGIENE_SKILL}}` — Sub-skill reference: how to create/update companies & contacts in your CRM |
| 18 | `{{LEAD_SCORING_SKILL}}` — Sub-skill reference: lead scoring & qualification methodology |
| 19 | `{{ALERT_FORMAT_SKILL}}` — Sub-skill reference: your alert formatting skill (optional — inline the format if you don't have one) |
| 20 | `{{HIGH_ACV_TAG}}` — Workspace tag marking high-ACV-potential accounts |
| 21 | `{{SELF_SERVE_THRESHOLD}}` — Company size below which accounts are self-serve (default: fewer than 30 employees) |
| 22 | `{{ALERT_TIERS}}` — Tiers that always alert on first touch (default: Gold, Diamond) |
| 23 | |
| 24 | |
| 25 | ## Signal type — read first |
| 26 | |
| 27 | Check the event type in the webhook payload before processing: |
| 28 | |
| 29 | **New comment** → full treatment (everything below). |
| 30 | **New reaction (like)** → light touch only: log to {{CRM}} + account |
| 31 | memory, then stop. No connection request. No Slack alert. |
| 32 | Exception: if the company is tagged {{ALERT_TIERS}}, or this is a repeated |
| 33 | engagement (2+ interactions), apply the full treatment. |
| 34 | |
| 35 | Comments and reactions are deliberately separate lanes: a comment is an |
| 36 | opinion someone attached their name to; a lone like is awareness at best — |
| 37 | volume is far higher and signal far lower. |
| 38 | |
| 39 | ## Engagement Process |
| 40 | |
| 41 | ### For Every ICP Lead/Agency Interaction |
| 42 | |
| 43 | When someone from an ICP company or relevant agency comments on or likes |
| 44 | {{PROFILE_OWNER}}'s post, **AND they match a relevant persona**: |
| 45 | |
| 46 | **Relevant personas** *(tune to your ICP's buying committee)*: |
| 47 | |
| 48 | Sales Leader (CRO, SVP Sales, VP Sales, Head of Sales, Director of Sales) |
| 49 | Growth Lead (Head of Growth, Director of Growth, VP Growth, or senior |
| 50 | marketing leader) |
| 51 | CEO (for companies in your core geographic/vertical segment) |
| 52 | Agency Owner (for agencies in your space) |
| 53 | GTM Engineer (GTM Engineer, Revenue Engineer, Marketing Engineer, Sales |
| 54 | Engineer focused on GTM infrastructure) |
| 55 | RevOps Lead, Head of Demand Gen, CMO |
| 56 | |
| 57 | **Ignore engagement from:** |
| 58 | |
| 59 | CFOs, finance roles |
| 60 | CTOs, engineers, technical roles (unless they're also founders/CEOs or |
| 61 | GTM-focused) |
| 62 | HR, operations, customer success |
| 63 | Individual contributors without buying responsibility (except the |
| 64 | engineer-persona exception above) |
| 65 | Your own team ({{INTERNAL_DOMAINS}} domain, or known names: |
| 66 | {{TEAM_MEMBERS}}) |
| 67 | Universities, academic institutions, professors, researchers |
| 68 | Companies below {{SELF_SERVE_THRESHOLD}} (self-serve) |
| 69 | |
| 70 | If the person is from an ICP company but NOT a relevant persona, ignore the |
| 71 | engagement entirely. |
| 72 | |
| 73 | #### Standard Processing (All ICP + Relevant Persona Engagers) |
| 74 | |
| 75 | **Check relationship status** — Are they a customer, active pipeline, or |
| 76 | closed-lost? If yes, acknowledge but don't run the standard engagement |
| 77 | flow. |
| 78 | **Mark awareness stage** — Update the company record to your Aware stage |
| 79 | if they're not already further along in the funnel. Never move a company |
| 80 | backwards. |
| 81 | **Update {{CRM}} + account memory** — Log the engagement (who, what they |
| 82 | said, which post) and update the account record. Follow |
| 83 | {{CRM_HYGIENE_SKILL}} for CRM writes. |
| 84 | **Run Lead Scoring** — After processing (only when the person belongs to |
| 85 | an identifiable company), run {{LEAD_SCORING_SKILL}}. LinkedIn engagement |
| 86 | is the lowest-weight signal — include it in the signal stack but do not |
| 87 | let it alone push an account above the second-lowest tier. |
| 88 | |
| 89 | #### High-Value Path (High ACV + Decision Maker Only) |
| 90 | |
| 91 | After standard processing, check if the engager's company has the |
| 92 | {{HIGH_ACV_TAG}} tag AND the engager is a strong buyer persona (CRO, VP |
| 93 | Sales, VP Marketing, CMO, CEO, Co-founder, RevOps Lead, Head of Demand Gen, |
| 94 | Agency Owner, or equivalent GTM leadership). |
| 95 | |
| 96 | If BOTH conditions are met: |
| 97 | |
| 98 | **Queue a LinkedIn connection request** from {{PROFILE_OWNER}}'s |
| 99 | account for approval. Connection requests carry no note by design |
| 100 | (better acceptance rates). Skip if already connected. |
| 101 | *(⚠️ Policy decision — see the checklist. The original deployment |
| 102 | auto-sent these with no approval for this narrow high-ACV + |
| 103 | decision-maker path; switch to auto-send only as a conscious opt-in.)* |
| 104 | **Post to {{ENGAGEMENT_CHANNEL}}** with: |
| 105 | Who engaged (name, title, company) |
| 106 | What they said (comment text) |
| 107 | Which post they commented on |
| 108 | ACV tier and why they qualify for the high-value path |
| 109 | A link to the engager's LinkedIn profile |
| 110 | |
| 111 | If either condition is NOT met (not high ACV, or not a decision maker) — |
| 112 | stop after standard processing. No connection request, no Slack post. The |
| 113 | engagement is logged and scored silently. |
| 114 | |
| 115 | ### Repeated Engagement (2+ Interactions) |
| 116 | |
| 117 | When the same ICP lead engages 2 or more times across {{PROFILE_OWNER}}'s |
| 118 | posts: |
| 119 | |
| 120 | **Active buyer check (run before any escalation):** verify the engager is |
| 121 | currently active in a buying role at the ICP company: |
| 122 | |
| 123 | Is the ICP company their primary, active role? If they have stepped back |
| 124 | (currently running a separate startup, recently founded a new company, or |
| 125 | no longer day-to-day there), treat them as a non-buyer and **stop — do not |
| 126 | surface, do not sequence, do not create a task**. |
| 127 | If their primary/active company is itself not an ICP fit (a 2-person |
| 128 | startup, a personal venture studio, or self-serve territory), stop. Do not |
| 129 | escalate on their nominal association with the larger company. |
| 130 | Partner-potential exception: a GTM operator, agency owner, or advisor who |
| 131 | might refer clients to you gets flagged to your partnerships owner instead |
| 132 | of routed as a buyer. |
| 133 | |
| 134 | If the active buyer check passes: |
| 135 | |
| 136 | **Move to high intent** — Update their stage to MQL (high intent signal) |
| 137 | **Build a multi-channel sequence** — Create a personalized multi-channel |
| 138 | campaign, queued for review (never sent automatically): |
| 139 | Open with a question tied to your product's core problem space |
| 140 | Personalize based on their engagement history and what they do |
| 141 | Use both LinkedIn and email if available |
| 142 | Reference their repeated engagement naturally |
| 143 | **Post to {{ENGAGEMENT_CHANNEL}}** flagging this as high-intent (2+ |
| 144 | interactions), include the full engagement history, and recommend |
| 145 | immediate follow-up. This notification fires regardless of ACV tier — |
| 146 | repeated engagement is always worth surfacing. |
| 147 | **Load {{ALERT_FORMAT_SKILL}}** for the alert format (or inline your |
| 148 | format here). |
| 149 | |
| 150 | **First-touch alert-tier rule:** Even on a first interaction, if the |
| 151 | engager's company is tagged {{ALERT_TIERS}}, immediately post to |
| 152 | {{ENGAGEMENT_CHANNEL}} with a high-priority flag. Do not wait for a second |
| 153 | interaction. |
| 154 | |
| 155 | ### Lead Magnet Posts |
| 156 | |
| 157 | Some posts may offer a lead magnet (e.g., "Comment X to get Y"). When this |
| 158 | happens: |
| 159 | |
| 160 | **Current lead magnet:** There is no active lead magnet at this time. Do |
| 161 | NOT share any URLs or documents. Treat commenters on lead magnet posts |
| 162 | with the standard processing flow. |
| 163 | **Future lead magnets** — {{PROFILE_OWNER}} updates this section before |
| 164 | each new lead magnet post with the post topic and corresponding URL. The |
| 165 | skill only ever shares the URL written here — never an inferred or |
| 166 | remembered one. |
| 167 | |
| 168 | ## Key Principles |
| 169 | |
| 170 | Track ALL comments and reactions (likes) from ICP companies and agencies |
| 171 | High-value path (connection request + Slack) only fires for high ACV + |
| 172 | decision maker — don't burn {{PROFILE_OWNER}}'s connection budget on |
| 173 | low-value targets |
| 174 | Repeated engagement always gets surfaced, regardless of ACV tier |
| 175 | Always personalize based on what they said |
| 176 | If outreach is needed, build the campaign — don't just recommend reaching |
| 177 | out |
| 178 | Keep initial outreach warm and helpful, not salesy |
| 179 | LinkedIn engagement is the lowest-weight signal — capped at the |
| 180 | second-lowest tier unless stacked with other signals |
| 181 | |
| 182 | |
| 183 | |
| 184 | ## What good looks like |
| 185 | |
| 186 | A great run processes only engagers who clear both gates — ICP company and buying persona — and the high-value path fires precisely: high-ACV tag plus decision maker, nothing else. Repeat engagers get a personalized multi-channel draft queued for review with their full engagement history attached, and every alert includes what the person actually said. |
| 187 | |
| 188 | Lone reactions stay in their light-touch lane, and repeat engagers who have stepped back from the ICP company get caught by the active-buyer check instead of escalated. |
| 189 | |
| 190 | Mediocre looks like: full-treatment alerts fired on a lone like, connection requests burned on individual contributors, engagement alone driving Gold or Diamond tiers, alerts without the comment text, or sequences going out without review. |
| 191 |
Discussion
Browse more free Claude skills or everything in Sales.