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.
SkillScore86Maintained
Automatic
◆Sales & GTM pack
Last verified 8/19/2026
What it changes
Passed 19 of 22 test cases with the skill, and 8 of 22 without it.
Without skill36%
With skill86%
Checks it passed that the model alone missed
Classifies the thread stage as Hot
Classifies the thread stage as Warm
Classifies the thread stage as Cool
and 12 more in the full report
11 fixed8 passed either way3 still failing0 broke
Pass-rate lift
+50 pp
Tokens
+56%
Agent turns
0%
Response time
-32%
Model gemini-3.6-flashMeasured 8/19/2026v119 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
What's inside
The instructions your model reads when the skill loads.
SKILL.md78 lines3 files
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.
Depends on APIFY_TOKEN. Without it, 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
Fetch user's recent comments. If APIFY_TOKEN is set, call lib.ApifyClient.fetch_user_recent_comments(username=<your-handle>, result_limit=30). Each item already includes the parent post body, post URL, post author, and reaction stats. If APIFY_TOKEN is not set, ask the user to list (or paste) the URLs of comments they've posted in the last 72h.
For each comment posted in last 72h: check the parent post's comment tree (use fetch_post_comments(post_id=..., scrape_replies=True)) for:
Replies to the user's comment
Whether the author posted any of those replies
Timestamps (time since user's comment, time since latest reply)
Classify stage:
Hot (<6h): author just replied. Respond within 90 min for max thread momentum
Warm (6-24h): the warm-reply window. Author replies most happen here
Cool (24-72h): still respondable but lower velocity
Dormant (>72h): don't reply in thread. Consider DM
Draft responses for warm threads using linkedin-reply-handler.
Flag suspicious patterns:
Author replied but also deleted someone else's comment (author is actively moderating, tread carefully)
Commenter is in thread self-promoting (your reply shouldn't engage them)
DM routing: if thread is dormant but the author engaged meaningfully, draft a DM that references the thread specifically.