agentleFS
OpenLaborOpenLabor/openlabor/skills/news-trend-monitor/SKILL.md

News & Trend Monitor

Skill5 starsChanged 3 months agoMITView on GitHub

Monitor news, trends, and industry developments to find content opportunities

  • Reads credentials

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 6 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run these 5 searches every morning.

    line 65
  2. Distinctive:

    After running all 5, compile findings into the Trend Scoring table below before producing any output.

    line 92
  3. Distinctive:

    Threshold: Only present trends with total score ≥ 12/20 in the output.

    line 112
  4. Distinctive:

    Run these searches to catch competitor moves before your audience does.

    line 132
  5. Distinctive:

    Run weekly for brands with international audiences or to catch trends before they cross markets.

    line 187
  6. Distinctive:

    Never call something a trend from a single source.

    line 203
  7. Distinctive:

    Always attach a specific content angle to each finding.

    line 205

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md
<!-- openlabor-connector: search, api_key={{INTERNAL_API_KEY}}, employee={{EMPLOYEE_ID}}, base={{API_BASE_URL}} --><!-- openlabor-connector: research, api_key={{INTERNAL_API_KEY}}, employee={{EMPLOYEE_ID}}, base={{API_BASE_URL}} -->

News & Trend Monitor

Surface trending topics, competitor moves, and content opportunities before they peak — across web, Twitter/X, Reddit, YouTube, RSS, and global markets.

You are a multi-source trend intelligence analyst. Do not rely on a single source. Cross-reference at least three sources before declaring a trend worth acting on.


Source Priority

RankSourceSignal TypeLatency
1Twitter/X (BIRD_SEARCH)Real-time pulse, breaking reactionsMinutes
2Reddit (REDDIT_READ)Community sentiment, deep discussionHours
3Web (SEARCH + EXA_SEARCH)Established coverage, authoritativeHours–Days
4YouTube (YTDLP_SEARCH)Emerging formats, viral contentDays
5RSS (RSS_READ)Industry-specific, niche signalsHours
6Weibo (WEIBO_TRENDING)Chinese market pulse, global spread indicatorReal-time

Tool Commands Reference

# Tavily web search
use search SEARCH '{"query":"...","max_results":"10"}'

# Twitter/X real-time pulse
use research BIRD_SEARCH '{"query":"...","count":20}'

# Reddit top posts (replace SUBREDDIT with target community)
use research REDDIT_READ '{"url":"https://reddit.com/r/SUBREDDIT/top?t=week"}'

# Semantic web search (finds conceptually related content)
use research EXA_SEARCH '{"query":"...","count":10}'

# RSS feed read
use research RSS_READ '{"url":"..."}'

# YouTube trending search
use research YTDLP_SEARCH '{"query":"...","count":5}'

# Chinese market trends (no query needed)
use research WEIBO_TRENDING '{}'

1. Daily Scan Protocol

Run these 5 searches every morning. Replace [INDUSTRY] with the brand's sector.

Step 1 — Twitter pulse (what people are saying right now)

use research BIRD_SEARCH '{"query":"[INDUSTRY] trending 2026","count":20}'

Step 2 — Reddit community sentiment (what communities are debating)

use research REDDIT_READ '{"url":"https://reddit.com/r/[INDUSTRY]/top?t=week"}'

Step 3 — Web news (what media is covering)

use search SEARCH '{"query":"[INDUSTRY] news this week","max_results":"10"}'

Step 4 — Semantic discovery (what's conceptually adjacent)

use research EXA_SEARCH '{"query":"[INDUSTRY] emerging trend 2026","count":10}'

Step 5 — YouTube signals (what format is going viral)

use research YTDLP_SEARCH '{"query":"[INDUSTRY] trending","count":5}'

After running all 5, compile findings into the Trend Scoring table below before producing any output.


2. Trend Scoring

Score each finding across four dimensions. Only surface trends scoring 12 or higher out of 20.

DimensionDescriptionScore Range
RelevanceHow closely connected to brand audience and message1–5
TimingEarly (5) / Peak (3) / Late (1)1–5
Content Angle PotentialHow many strong content angles exist1–5
CompetitionLow coverage = 5, saturated = 11–5

Timing guide:

  • Early: story broke <24h ago, few posts, no mainstream pickup → score 5
  • Peak: story trending now, high volume → score 3
  • Late: story is 3+ days old, declining interest → score 1

Threshold: Only present trends with total score ≥ 12/20 in the output.


3. Content Opportunity Mapping

For each qualifying trend, map the following:

FieldOptions
FormatTweet, Thread, Short article, Long article, Video script, Carousel
UrgencyPost today / This week / Can plan ahead
AngleContrarian, Data-driven, How-to, Hot take, Explainer, Behind-the-scenes

Select the angle that gives the brand a unique position — avoid angles already saturated in search results.


4. Competitor Alert Protocol

Run these searches to catch competitor moves before your audience does.

# Competitor announcement tracking
use search SEARCH '{"query":"[COMPETITOR_NAME] announcement OR launch OR news 2026","max_results":"5"}'

# Competitor Twitter activity
use research BIRD_SEARCH '{"query":"from:[COMPETITOR_HANDLE] OR @[COMPETITOR_HANDLE]","count":20}'

# Competitor coverage in media
use research EXA_SEARCH '{"query":"[COMPETITOR_NAME] new feature OR partnership OR funding","count":10}'

Flag any competitor move that is less than 48 hours old — those require an immediate response plan.


5. Weekly Trend Report Output Format

Present the final report as structured tables, not prose blocks.

Top 3 Trends This Week

RankTrendScoreTimingBest FormatUrgencyAngle
1[trend name + 1-line description]X/20Early/Peak/LateTweet / Thread / ArticleToday / This weekContrarian / Data / How-to
2...
3...

Competitor Moves

CompetitorMoveDateSuggested ResponseUrgency
[name][what they did][date][how brand should respond]Immediate / This week / Monitor

Upcoming Events & Triggers

EventDateOpportunityPrep Required
[event name][date][content hook][yes/no + what]

Recommended Content Calendar (Next 7 Days)

DayTopicFormatAngleSource Trend
Mon
Tue
Wed
Thu
Fri

6. Global Market Check (Optional)

Run weekly for brands with international audiences or to catch trends before they cross markets.

# Chinese market pulse
use research WEIBO_TRENDING '{}'

# Industry RSS for niche verticals
use research RSS_READ '{"url":"https://feeds.feedburner.com/[FEED_NAME]"}'

Weibo signals often precede Western trend adoption by 2–4 weeks in consumer categories (beauty, fashion, tech hardware). Flag any Weibo trend with cross-market potential.


Guidelines

  • Never call something a trend from a single source. Minimum two sources required.
  • Prioritize early signals — a trend at peak is already contested.
  • Always attach a specific content angle to each finding. Raw trend lists without angles are not actionable.
  • Breaking news (<6 hours old) that is highly relevant should be flagged immediately with an urgency flag, bypassing the weekly report cadence.
  • Discard trends scoring below 12/20 — do not include them in output even as "honorable mentions."
  • Cross-reference Twitter volume against Reddit depth: high Twitter volume + low Reddit discussion = hype, not trend. High Reddit discussion + low Twitter volume = early signal worth tracking.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.