agentleFS
styfinitystyfinity/linkedin-engine/skills/linkedin-engager-analytics/SKILL.md

linkedin-engager-analytics

Skill9 starsChanged 4 months agoMITView on GitHub

Analyse everyone who liked or commented on a post, score them against your ICP, and return the match rate plus the top 10 profiles with a real-signal outreach note for each. Use after a post lands to find the warm prospects hiding in your engagement.

7 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 7 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every post that lands buries warm prospects in its likes and comments.

    line 9
  2. Distinctive:

    Every outreach note must cite a real, specific signal.

    line 28
  3. Distinctive:

    No invented titles, companies, or signals.

    line 29
  4. Distinctive:

    No em-dashes. No guaranteed-result promises.

    line 30

“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

LinkedIn Engager Analytics

Every post that lands buries warm prospects in its likes and comments. This skill pulls them out, scores them, and hands you the ones worth a conversation.

Inputs

  • A post URL (pulled live if the LinkedIn CLI/MCP layer is connected) OR a pasted list of engagers with name, title, company: $ARGUMENTS
  • The brief (ICP, persona, pains, offer) loads automatically.

Do this

  1. Get the engagers. Live via the connected LinkedIn CLI/MCP layer if it is wired in. If it is not, work off the pasted list and say so in one line.
  2. Score each engager against the brief's ICP, 0 to 100, on title, seniority, company size, industry, and any buying signal. Show the score logic in one phrase per person.
  3. Compute the ICP match rate: the share of total engagers who clear the fit bar.
  4. Rank everyone and return the top 10. For each, write a one-line outreach note that references their REAL signal: the exact comment they left, their role, or a recent post of theirs. No generic openers.
  5. Flag the 3 hottest profiles to action first.

Output

Lead with the ICP match rate headline (e.g. "31% of 64 engagers fit the ICP"). Then a top-10 table: name, title, company, score, outreach note. Then a short "Action these 3 first" list, ready to hand to /linkedin-outreach. Run any draft note through /linkedin-humanizer before it goes out.

Rules

  • Pulling live engagers needs the connected CLI/MCP layer. Without it, state plainly that you are scoring the pasted list only.
  • Draft notes only. Nothing sends from this skill. Sending happens through the opt-in CLI/MCP layer, on explicit approval, capped at 20 actions a day for new accounts.
  • Every outreach note must cite a real, specific signal. If a person's signal is just a like with no comment, say so and rank accordingly.
  • No invented titles, companies, or signals. If a field is missing, mark it unknown rather than guessing.
  • No em-dashes. No guaranteed-result promises.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.