playbook-linkedin-engagement

Converts LinkedIn post engagers into ICP-filtered prospect rows with source-company exclusion and DNC suppression.

Updated May 28, 2025
One-click install
npx skills add https://github.com/meloShaya/insteltech --skill playbook-linkedin-engagement-meloshaya
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: playbook-linkedin-engagement
Source: https://github.com/meloShaya/insteltech/tree/main/crm/library/skills/playbooks/playbook-linkedin-engagement
Command: npx skills add https://github.com/meloShaya/insteltech --skill playbook-linkedin-engagement-meloshaya

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Scraping people who like or comment on a competitor's or customer's LinkedIn posts produces raw lists full of unusable contacts — including the source company's own employees — and roughly 9 in 10 engagers fail ICP filtering, wasting enrichment spend. This playbook defines the gating, suppression, and cost-planning rules that turn that raw engagement signal into clean prospect rows. ## Core Features & Use Cases - Source-company exclusion rule: Drops every engager employed by any source company using four match paths (resolved domain, email domain, profile URL, squashed name), and pushes source companies onto the client's do-not-contact list. - ICP gating before paid calls: Applies headcount, country, and title filters plus suppression checks (client DNC, existing TAM, live campaigns) so email finding runs only on the ~10% of survivors. - Clay implementation specs: Provides both a Clay table column design and a Clay workflow graph with precondition checks that refuse to run on unresolved sources or missing ICP data. - Use Case: A sales team wants prospects from people commenting on a competitor's posts. The playbook harvests reactions and comments from shortlisted posts, drops the competitor's own staff, filters by ICP, and outputs one prospect row per surviving engager with evidence URLs. ## Quick Start Ask the assistant to harvest engagers from a specific competitor's LinkedIn posts, filter them against your ICP, and output one prospect row per surviving engager.

Frequently Asked Questions about playbook-linkedin-engagement

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build a prospect list from LinkedIn post engagers?

Harvest reactions and comments from shortlisted posts, then gate engagers through source-company exclusion, ICP filters on headcount and country, and suppression checks before email finding. Only about 1 in 10 raw engagers survives, so plan to harvest 10-15x your target.

How do I exclude a competitor's own employees from an engagement list?

Match each engager's employer on resolved domain first, then profile URL, then squashed name, and also on resolved email domain. Name matching alone misses most employees because employer strings are spelled inconsistently in scraped data.

Should I use a Clay table or Clay workflow for LinkedIn engagement scraping?

A workflow suits the harvest because it is one-to-many, fanning one source URL into hundreds of engager records. A table works for the per-row gate and enrichment after you import harvested rows, with all paid columns gated on survival.

Why does my LinkedIn engagement list contain the client's own employees?

The client's domain got into the source set, which means the source list is wrong and the run should stop. Never block the client's own domain; fix the source list instead of filtering around it.

What does LinkedIn engagement scraping cost per usable prospect?

Cost is about $4.45 per 1,000 raw engagers, which works out to roughly $45 per 1,000 usable prospects at the measured ~10% survival rate. Shortlisting posts by engagement count before scraping is the cheapest cost lever.

When should I not use LinkedIn engagement harvesting for prospecting?

Do not use it to find more companies in a market or similar companies (use a lookalikes playbook) or to track job changers (use a new-in-role playbook). It only fits when a source account's audience is the client's audience.