← Back to list
linkedin-thread-monitor Checked
Track which of your LinkedIn comments earned author replies. Flags the 6-24h warm-reply window wh…
9.1Overall rating
Installation
🤖 Install via AI
Copy the prompt below and send it to your AI assistant (e.g. Claude Code) — it will follow the instructions and install automatically.
Install the "linkedin-thread-monitor" skill by following the instructions at https://skill123.me/install/linkedin-thread-monitor.
⌨️ Command line install
Run in your terminal — downloads and installs to ~/.claude/skills/.
curl -fsSL https://skill123.me/install/linkedin-thread-monitor.sh | bash
📦 Download ZIP
Download the zip and extract it into your skills directory (e.g. ~/.claude/skills/), then restart your session.
⬇ Download v1.0.0 · 6 KBAbout this skill
Overview
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).
Source
- Repo: https://github.com/sergebulaev/linkedin-skills
- Path: skills/linkedin-thread-monitor
Score breakdown
Trigger
9.5
What/When plus explicit Not-For versus engager-analytics; clear trigger phrases.
Structure
9.3
Compact 101-line SKILL.md with output spec and timing matrix references.
Workflow
8.4
Stage classification with response deadlines, paste fallback, cost accounting, routing to sibling skills; no automated scheduling loop.
Content
9.0
Concrete timing distribution and hard rules; mostly crisp with minor anecdotal anchoring.
Engineering
9.0
Correct frontmatter; lib dependency exists in bundle; references present.
Security
9.5
Own-account public data only, no login or cookies; untrusted-content rules inline; DM drafting gated to user review.
Tracks the user is own comments and author replies via no-cookie public Apify actors, classifies hot/warm/cool/dormant with a timing matrix, and routes warm threads to reply-handler. Paste fallback without token; all data stays local with only Apify seeing requests; inline injection defenses.