Agent skill · Content & Marketing

kol-content-monitor

Track what key opinion leaders (KOLs) in your space are posting on LinkedIn and Twitter/X. Surfaces trending narratives, high-engagement topics, and early signals of emerging conversations before they peak. Chains linkedin-profile-post-scraper and twitter-mention-tracker. Use when a marketing team wants to ride trends rather than create them from scratch, or when a founder wants to know which topics are resonating with their audience.

gooseworks-aigithub.com/gooseworks-aiGitHub ↗
claude-codecodexcursorMIT
Install
npx skills add gooseworks-ai/goose-skills --skill kol-content-monitor --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 7 KB
Bundled scripts: none
Path: skills/monitoring/composites/kol-content-monitor/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,091
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# KOL Content Monitor Track what Key Opinion Leaders in your space are writing about. Surface trending narratives early — before they peak — so your team can join the conversation at the right time with relevant content. **Core principle:** For seed-stage teams, the fastest path to content distribution is riding a wave that's already breaking, not creating one from scratch. ## When to Use - "What are the top voices in [our space] posting about?" - "What topics are trending on LinkedIn in [industry]?" - "I want to know what content is resonating before I write anything" - "Track [list of founders/experts] and tell me what they're saying" - "Find trending narratives I can contribute to" ## Phase 0: Intake ### KOL List 1. Names and LinkedIn URLs of KOLs to track (if known) - If unknown: use `kol-discovery` skill first to build the list 2. Twitter/X handles for the same KOLs (optional but recommended for full picture) 3. Any specific topics/keywords you care about? (for filtering noisy feeds) ### Scope 4. How far back? (default: 7 days for weekly monitor, 30 days for first run) 5. Minimum engagement threshold to include a post? (default: 20 reactions/likes) Save config to the current w

What's inside
Steps it walks through
  1. When to Use
  2. Phase 0: Intake
  3. KOL List
  4. Scope
  5. Phase 1: Scrape LinkedIn Posts
  6. Phase 2: Scrape Twitter/X Posts
  7. Phase 3: Topic Clustering
  8. Clustering approach:
  9. Signal types to flag:
  10. Phase 4: Output Format
  11. Phase 5: Build Trigger-Based Content Calendar
  12. Scheduling
  13. Cost
  14. Tools Required
Ships with 1 file
  • skill.meta.json
Commands it runs
python3 skills/linkedin-profile-post-scraper/scripts/scrape_linkedin_posts.py \
python3 skills/twitter-mention-tracker/scripts/search_twitter.py \
More from goose-skills
All skills →
About this skill
What does the kol-content-monitor skill do?

Track what key opinion leaders (KOLs) in your space are posting on LinkedIn and Twitter/X. Surfaces trending narratives, high-engagement topics, and early signals of emerging conversations before they peak. Chains linkedin-profile-post-scraper and twitter-mention-tracker. Use when a marketing team wants to ride trends rather than create them from scratch, or when a founder wants to know which topics are resonating with their audience.

How do I install it?

Run `npx skills add gooseworks-ai/goose-skills --skill kol-content-monitor --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From gooseworks-ai/goose-skills, a repository with 1,091 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going