agentleFS
claude-worldclaude-world/claude-agent/.claude/skills/trend-scout/SKILL.md

trend-scout

Skill5 starsChanged 8 months agoMITView on GitHub

Discover trending topics from 20 free sources (Google Trends, HackerNews, Reddit, GitHub, Product Hunt, etc.) with no API keys required. Returns trend summaries with velocity and context. Use when user asks "what's trending", "any hot topics", "what's popular right now".

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 3 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

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

    Call get_trending(sources="", geo=<geo>, count=20) to query all 20 sources simultaneously.

    line 39
  2. Very specific:

    If a keyword was provided, also call search_trends(query=<keyword>) for cross-source results.

    line 41
  3. Distinctive:

    Fallback: If trend-pulse MCP is unavailable, use WebSearch for "trending topics today [geo]" and format results manually.

    line 43
  4. Very specific:

    Call take_snapshot() to save current trends for future velocity tracking.

    line 52
  5. Distinctive:

    Keep output under 300 words

    line 74
  6. Distinctive:

    If no trends found for a keyword, say so and suggest broader search

    line 77

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “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

Trend Scout

You are the trend discovery skill for Claude-Agent. Surface what's trending right now from 20 free sources.

Input

$ARGUMENTS — optional geo tag (TW, US, JP) and/or keyword filter.

Steps

1. Parse Arguments

  • Extract geo code if present (default: no filter = world)
  • Extract keyword filter if present

2. Fetch Trends

Call get_trending(sources="", geo=<geo>, count=20) to query all 20 sources simultaneously.

If a keyword was provided, also call search_trends(query=<keyword>) for cross-source results.

Fallback: If trend-pulse MCP is unavailable, use WebSearch for "trending topics today [geo]" and format results manually.

3. Enrich Top Results

For the top 3-5 trends, call get_trend_history(topic=<name>) to get:

  • Velocity (rising/stable/declining)
  • How long it's been trending
  • Direction signal

4. Save Snapshot

Call take_snapshot() to save current trends for future velocity tracking.

5. Format Output

TRENDING NOW [geo/worldwide]

1. [Topic] — [Source] | [velocity: rising/stable]
   Brief: [1-sentence context]

2. [Topic] — [Source] | [velocity]
   Brief: [1-sentence context]

3-5. ...

Sources queried: [N] | Snapshot saved: [timestamp]

6. Suggest Follow-up

End with: "Want me to create a post about any of these? Or dig deeper into one?"

Rules

  • Keep output under 300 words
  • Show source name for each trend (Google Trends, HN, Reddit, etc.)
  • Include velocity direction when available
  • If no trends found for a keyword, say so and suggest broader search
  • Save substantive results to workspace/trends-YYYY-MM-DD.md

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.