{"id":"linkedin-thread-monitor","name":"linkedin-thread-monitor","summary":"あなたのLinkedInコメントのうち、どのコメントが著者の返信を得たかを追跡しましょう。スレッドの勢いがピークに達する6〜24時間のウォーム返信ウィンドウをフラグ付けし、スレッドをホット/ウォーム/クール/休眠に分類し、ウォームスレッドをLinkedIn-reply-handlerにルーティングしてフォローアップド…","body":"# LinkedIn Thread Monitor\n\nTrack 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.\n\nDepends on `APIFY_TOKEN`. Without it, falls back to user-paste of recent comment URLs.\n\n## When to use\n\n- Daily: \"What threads need follow-up today?\"\n- After posting a batch of comments: \"Check back in 6 hours\"\n- When an author replied personally: \"Draft the response\"\n\n## Input\n\n- Your LinkedIn handle (last path segment of profile URL, e.g. `your-handle`)\n- Optional: window in hours (default 72)\n\n## Output\n\nOutput 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.\n\n## Steps\n\n1. **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.\n2. **For each comment posted in last 72h:** check the parent post's comment tree (use `fetch_post_comments(post_id=..., scrape_replies=True)`) for:\n   - Replies to the user's comment\n   - Whether the author posted any of those replies\n   - Timestamps (time since user's comment, time since latest reply)\n3. **Classify stage:**\n   - Hot (<6h): author just replied. Respond within 90 min for max thread momentum\n   - Warm (6-24h): the warm-reply window. Author replies most happen here\n   - Cool (24-72h): still respondable but lower velocity\n   - Dormant (>72h): don't reply in thread. Consider DM\n4. **Draft responses** for warm threads using `linkedin-reply-handler`.\n5. **Flag suspicious patterns:**\n   - Author replied but also deleted someone else's comment (author is actively moderating, tread carefully)\n   - Commenter is in thread self-promoting (your reply shouldn't engage them)\n6. **DM routing:** if thread is dormant but the author engaged meaningfully, draft a DM that references the thread specifically.\n\n## Warm-reply window\n\nAnchored to a 2026-04 data point: a CEO replied to Serge's comment 22h after the original post. Reply-rate distribution: 0-6h 70%, 6-24h 25% (higher quality), >24h rare. Follow-up timing: 0-6h reply respond within 90 min; 6-24h within 2h; >24h within 4h before it goes cold. See `references/thread-timing.md` for the full matrix.\n\n## Inbound-quality signals\n\nHigh-quality = follow up: founder/operator title, company in ICP, active posting history, >10 mutual 2nd-degree connections, prior thoughtful comments on user's posts.\n\nLow-quality = skip: generic praise, template language (\"I'd love to hop on a quick call\"), sales/agency profile with no operator history, same comment copy-pasted across many creators.\n\n## Hard rules\n\nGlobal voice rules: see root `SKILL.md` §Voice rules. Additional skill-specific rules:\n\n- Never reply to a reply later than 72h after the thread's last turn. Switch to DM.\n- Never chain 3+ replies under one comment (thread spam).\n- If the author deleted their reply, do not reply. They reconsidered.\n- Don't DM a warm thread before first replying publicly (skips a step).\n\n## Cost accounting\n\n| Action | Apify call | Cost (free tier) |\n|---|---|---|\n| Daily thread sweep (1 user, ~30 comments) | `fetch_user_recent_comments` once | $0.005 |\n| Per-warm-thread context | `fetch_post_comments(scrape_replies=True)` | $0.005 each |\n\nA typical creator running this skill 5 days/week stays well under the $5 free monthly credit.\n\n## Files\n\n- `SKILL.md` — this file\n- `references/output-spec.md` — daily report shape, warm-thread preview, weekly roll-up, sample run\n- `references/thread-timing.md` — the timing matrix with examples\n\n## Related skills\n\n- `linkedin-reply-handler` — drafts the actual follow-up message for warm threads\n- `linkedin-engager-analytics` — analyze who liked/commented on a post (different surface)\n- `linkedin-comment-drafter` — drafts the initial comment that starts threads","author":"@sergebulaev","ownerProfile":null,"authorContacts":null,"sourceUrl":"https://github.com/sergebulaev/linkedin-skills/tree/main/.codex-marketplace/linkedin-skills/skills/linkedin-thread-monitor","license":"MIT","category":"document","lang":"en","tokens":1014,"stars":0,"calls30d":2,"claimed":false,"visibility":"public","origin":"crawler","version":"0.1.0","createdAt":"2026-08-22","updatedAt":"2026-08-22","files":[{"path":"references/output-spec.md","size":1219,"sha256":"462d8f001365c3a28ca4668e3adf3dadbc953ab97cf66033c1da845573fbc260"},{"path":"references/thread-timing.md","size":3770,"sha256":"ce75e56ee61a1fc682990dbc49c197c50da49ec4ff38e55fd3ba70b4f7bfb196"}],"requires":{"mcp":[],"tools":[]},"safety":{"flags":[],"scannedAt":"2026-08-22","hasScripts":false,"networkEndpoints":[]}}