Skip to content

sergebulaev/linkedin-skills / .codex-marketplace/linkedin-skills/skills/linkedin-thread-monitor

linkedin-thread-monitor

Verified

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).

FileKindSize
SKILL.mdskill md5.8 KB
references/output-spec.mdmarkdown1.2 KB
references/thread-timing.mdmarkdown3.7 KB

references/output-spec.md

View on GitHub
# Mode 1. Thread monitoring — output spec

Canonical sample outputs for the daily thread-monitoring report. See `SKILL.md` for the workflow steps.

## Daily report

| Posted | Author | Post | Comment | Reply? | Stage | Action |
|---|---|---|---|---|---|---|
| 18h ago | Author A | SaaS Co. | "moat moved to taste" | author replied 14h ago | Warm (6-24h window) | Reply now |
| 22h ago | Author B | Enterprise SaaS | "integration depth moat" | No | Cold | Skip |
| 3h ago | Author C | AI vendor | "twin economies" | No | Watch | Check in 3h |

## For each warm thread

- Thread preview (last 3 turns)
- Suggested response (drafted via `linkedin-reply-handler`)
- Reaction target (the specific reply URN, not the post)
- Priority (high / medium / low)

## Weekly roll-up

- Total comments posted
- Author-reply rate (target 15%+)
- Conversion to DM (when thread closes warm)

## Example run

> Input: monitor sbulaev profile, last 24h

> Output:
> - 1 warm thread: the author replied 14h ago on their post. Current stage: Warm (8-24h). Suggested response ready. Action: post within 2 hours.
> - 8 cold threads (no author engagement). Skip.
> - 3 watching threads (<6h old, author may still reply). Check again in 3-6h.
deprecation-and-migrationaddyosmani/agent-skillsManages deprecation and migration. Use when removing old systems, APIs, or features. Use when migrating users from one implementation to another. Use when migrating a database schema in production, such as renaming or dropping a column without downtime (expand/contract). Use when deciding whether to maintain or sunset existing code.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
performance-optimizationaddyosmani/agent-skillsOptimizes application performance across frontend, backend, queries, and databases. Use when performance requirements exist, when you suspect performance regressions, when Core Web Vitals or load times need improvement, when N+1 query patterns need fixing, or when profiling reveals bottlenecks.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
agent-cost-reportthedotmack/claude-memBelievable agent cost report for any period, default the last 7 full days PT, not counting today. Measured tokens from Claude Code transcripts priced at OpenRouter list prices (ESTIMATED), measured provider spend when a sanctioned source exists, note-taker cost separate, Timing-style HTML/PDF plus report.json, line-items.csv, evidence.json.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
agent-cost-reportthedotmack/claude-memBelievable agent cost report for any period, default the last 7 full days PT, not counting today. Measured tokens from Claude Code transcripts priced at OpenRouter list prices (ESTIMATED), measured provider spend when a sanctioned source exists, note-taker cost separate, Timing-style HTML/PDF plus report.json, line-items.csv, evidence.json.Stars: 118kUpdated Claude CodeCodexVerifiedInstall