linkedin-engager-analytics SKILL.md skillA
linkedin-engager-analytics from sergebulaev/linkedin-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add sergebulaev/linkedin-skills/linkedin-engager-analytics@git:20261015.aaa47eaPins git:20261015.aaa47ea in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- sergebulaev/linkedin-skills
- Path
skills/linkedin-engager-analytics/SKILL.md- Versions recorded
- 6
- Latest version
- git:20261015.aaa47ea, committed Oct 15, 2026
- First version recorded
- May 11, 2026
- Size
- 6,122 bytes
- Repository stars
- 5,014
- License
- MIT
Pull the people who liked or commented on any LinkedIn post and segment them by ICP fit (peer / aspirational / prospect / other). Produces an engager roster, tier breakdown, and outbound action lists (follow back, comment-drop, DM-able with one-line openers). Powered by Apify, no LinkedIn login. Triggers on "who liked my post", "who engaged", "engagers report", "audience analytics". Not for tracking author replies to your comments (use linkedin-thread-monitor).
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# LinkedIn Engager Analytics Pull every liker and commenter on a LinkedIn post and bucket them by ICP fit. Outputs a roster + action list you can feed into your DM or outreach queue. Needs a read credential: `APIFY_TOKEN`, or the Apify MCP connector (the only option on claude.ai). With neither, falls back to user-paste of the engager list. ## When to use - After publishing a post: "Who actually engaged? Are they ICP?" - Before a campaign: "Pull the last 5 viral posts in my niche, group their commenters by company size" - Reviewing competitor engagement: which prospects show up across multiple authors ## Input - One or more LinkedIn post URLs - Optional: ICP definition (target titles, company size, industry) - Optional: max engagers per post (default 100) ## Output Output format (engager roster, tier breakdown, action lists): see `references/output-spec.md`. Headline: a table of engagers labelled by ICP tier and a per-tier action list. ## Steps …
Read the whole file at its exact version.
How to install
mdr add sergebulaev/linkedin-skills/linkedin-engager-analytics@sha256:4fd73bc68a5bdcfeThe line at the top of this page pins the label git:20261015.aaa47ea, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_dmljfremhnv2wb6m)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 6 versions of this file, between May 11, 2026 and Oct 15, 2026, about one every 31 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261015.aaa47ea latest | 2026-10-15 | aaa47ea | 6,122 B | A | view · diff |
| git:20260915.3cb3022 | 2026-09-15 | 3cb3022 | 5,776 B | A | view · diff |
| git:20260909.093982e | 2026-09-09 | 093982e | 5,555 B | A | view · diff |
| git:20260903.bb42f73 | 2026-09-03 | bb42f73 | 5,545 B | A | view · diff |
| git:20260521.65b8a91 | 2026-05-21 | 65b8a91 | 4,633 B | A | view · diff |
| git:20260511.c8f8489 | 2026-05-11 | c8f8489 | 4,639 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (6122 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
sergebulaev/linkedin-skills · 5,014 stars · license MIT · pushed 2026-10-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_dmljfremhnv2wb6m GET https://markdownregistry.com/api/v1/resolve?ref=sergebulaev/linkedin-skills/linkedin-engager-analytics GET https://markdownregistry.com/api/v1/blob/4fd73bc68a5bdcfe77947c0e1dc5e99add840e6feb6b9af603d9e3a2ad95e4f1
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from sergebulaev/linkedin-skills
Every file in sergebulaev/linkedin-skills