linkedin-thread-monitor SKILL.md skillA
linkedin-thread-monitor 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-thread-monitor@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
.codex-marketplace/linkedin-skills/skills/linkedin-thread-monitor/SKILL.md- Versions recorded
- 7
- Latest version
- git:20261015.aaa47ea, committed Oct 15, 2026
- First version recorded
- May 19, 2026
- Size
- 5,916 bytes
- Repository stars
- 5,014
- License
- MIT
Track which of your LinkedIn comments earned author replies. Flags the 6-24h warm-reply window where thread momentum peaks, classifies threads as hot/warm/cool/dormant, and routes warm ones to linkedin-reply-handler for follow-up drafts. Powered by Apify, no LinkedIn login. Triggers on "what threads need follow-up", "author replied", "monitor my comments". Not for analyzing likers on a post (use linkedin-engager-analytics).
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 Thread Monitor Track which of your comments earned author replies. The author-reply signal is the highest-value inbound LinkedIn produces; this skill ensures you respond inside the window where momentum compounds. 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 recent comment URLs. ## When to use - Daily: "What threads need follow-up today?" - After posting a batch of comments: "Check back in 6 hours" - When an author replied personally: "Draft the response" ## Input - Your LinkedIn handle (last path segment of profile URL, e.g. `your-handle`) - Optional: window in hours (default 72) ## Output Output format (daily report, warm-thread preview, weekly roll-up): see `references/output-spec.md`. Headline: a table of recent comments with author-reply status + recommended action. ## Steps …
Read the whole file at its exact version.
How to install
mdr add sergebulaev/linkedin-skills/linkedin-thread-monitor@sha256:8395be552396a57eThe 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_aka7ma7x5iwvvtuf)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 7 versions of this file, between May 19, 2026 and Oct 15, 2026, about one every 25 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261015.aaa47ea latest | 2026-10-15 | aaa47ea | 5,916 B | A | view · diff |
| git:20260915.321dda7 | 2026-09-15 | 321dda7 | 5,601 B | A | view · diff |
| git:20260915.3cb3022 | 2026-09-15 | 3cb3022 | 5,535 B | A | view · diff |
| git:20260909.093982e | 2026-09-09 | 093982e | 5,572 B | A | view · diff |
| git:20260903.bb42f73 | 2026-09-03 | bb42f73 | 5,564 B | A | view · diff |
| git:20260521.65b8a91 | 2026-05-21 | 65b8a91 | 4,652 B | A | view · diff |
| git:20260519.c627455 | 2026-05-19 | c627455 | 4,654 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 (5916 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_aka7ma7x5iwvvtuf GET https://markdownregistry.com/api/v1/resolve?ref=sergebulaev/linkedin-skills/linkedin-thread-monitor GET https://markdownregistry.com/api/v1/blob/8395be552396a57ea01fb4299c5ab8aa90ab1cfcae8fc5e8d9d284e3000a90b5
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