agentleFS
asoisoasoiso/trend-radar/trend-monitor/SKILL.md

trend-monitor

Skill2 starsChanged 7 months agoApache-2.0View on GitHub

Sweep current cross-platform hotspots and surface emerging keywords from the latest crawl batch. Use when the user asks 今日热点 / 今天有什么热点 / 今天热搜 / 各平台热搜 / 看一下当前热搜 / 现在在火什么 / 全网热点 / 全网在聊什么 / what's trending / what's trending now / multi-platform trend sweep / hotspot snapshot, or wants a quick snapshot of zhihu / weibo / douyin / bilibili / toutiao / baidu / thepaper / ifeng / tieba / cls-hot / wallstreetcn-hot at once via the trendradar MCP. Combines latest news with both preset-keyword extraction and emergent auto-extraction so the agent can flag 全网共振 (cross-platform resonance) and 新冒头 (newly emerging) terms in a single pass.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. gokulsvision/Crewm8-Social-Media-Manager-Skill-Graph★ 17same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository4 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 6

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Distinctive:

    If the user names a single article, a specific topic deep-dive, or a date in the past, this is not the right skill — defer to a …

    line 20
  2. Very specific:

    Resolve the time window: If the user mentions any date that isn't "now / 现在 / 今天 / today", call mcp__trendradar__resolve_date_range first …

    line 24
  3. Very specific:

    Pull the latest news batch: Call mcp__trendradar__get_latest_news with limit=80 and include_url=False.

    line 26
  4. Very specific:

    get_latest_news returns empty / very stale: Call mcp__trendradar__get_system_status to check crawl freshness.

    line 104
  5. Distinctive:

    Don't paginate huge lists.

    line 112
  6. Very specific:

    Don't include URLs unless the user explicitly asked for them.

    line 113
  7. Very specific:

    Don't fabricate trend data when MCP fails.

    line 114
  8. Distinctive:

    Don't merge preset-keyword and auto-extract output into one undifferentiated list.

    line 115
  9. Very specific:

    Don't issue the two get_trending_topics calls sequentially.

    line 116

≈ “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

trend-monitor

Multi-platform hotspot sweep. Pulls the latest crawl batch from the trendradar MCP, runs preset-focus and emergent keyword extraction in parallel, then summarizes either by platform or by topic.

When to activate

Trigger on phrases like:

  • 今日热点 / 今天有什么热点 / 今天热搜
  • 各平台热搜 / 看一下当前热搜 / 全网热点 / 全网在聊什么
  • 现在在火什么 / 最近在聊什么
  • what's trending / what's trending now / multi-platform sweep / hotspot snapshot
  • 给我看一下 zhihu / weibo / douyin / bilibili / toutiao / baidu / thepaper / ifeng / tieba / cls-hot / wallstreetcn-hot 的热搜

If the user names a single article, a specific topic deep-dive, or a date in the past, this is not the right skill — defer to a search/topic-analysis skill instead. This skill is for the live cross-platform snapshot.

Workflow

  1. Resolve the time window. If the user mentions any date that isn't "now / 现在 / 今天 / today", call mcp__trendradar__resolve_date_range first and reuse that range in the next steps. For "今天 / now / latest", skip this step.
  2. Pull the latest news batch. Call mcp__trendradar__get_latest_news with limit=80 and include_url=False. Set include_url=True only if the user explicitly asked for links. If the user named specific platforms, pass platforms=[...] (e.g. ["weibo", "zhihu"]); otherwise let the tool return the full set.
  3. Run keyword extraction in parallel. Issue both calls in the same response:
    • mcp__trendradar__get_trending_topics with extract_mode="keywords", top_n=20 — preset focus list (curated themes the project tracks).
    • mcp__trendradar__get_trending_topics with extract_mode="auto_extract", top_n=20 — emergent terms surfaced from this batch only.
  4. Cross-reference. Build two buckets before drafting the output:
    • 全网共振: keywords that appear on ≥3 platforms in this batch (pulled from either extraction mode).
    • 新冒头: terms present in auto_extract results but absent from the keywords preset list — these are the emergent signals worth flagging.
  5. Pick the output template based on user intent (see "Output templates" below). Default to 平台分组视图 unless the user asked for themes / topics / "what's everyone talking about across platforms".

Output templates

Pick one. Both end with the same closing block.

平台分组视图 (default)

# 今日全网热点 · <YYYY-MM-DD HH:mm>

## 微博 (weibo)
1. <标题> · 热度 <metric>
2. ...
(top 5)

## 知乎 (zhihu)
1. ...
(top 5)

## 抖音 (douyin)
...

## B站 (bilibili)
...

(只列出本批次实际有数据的平台,每个平台 top 5)

---

### 全网共振
- **<关键词>** — 出现在 weibo / zhihu / toutiao(3 个平台)
- **<关键词>** — 出现在 weibo / douyin / bilibili / baidu(4 个平台)

### 新冒头 (auto-extract only)
- **<新词>** — 首次在本批次浮现,主要源自 <平台>
- **<新词>** — ...

主题分组视图 (when user asks for cross-platform themes)

# 今日热点主题 · <YYYY-MM-DD HH:mm>

## <主题 / 关键词>
- 微博 #2: <标题片段>
- 知乎 #5: <标题片段>
- 抖音 #1: <标题片段>

## <主题 / 关键词>
- 头条 #3: ...
- 百度 #7: ...

(每个主题列出实际证据:哪个平台、第几名、标题片段)

---

### 全网共振
- **<关键词>** — 出现在 X / Y / Z(N 个平台)

### 新冒头 (auto-extract only)
- **<新词>** — 首次在本批次浮现,主要源自 <平台>

Both templates: keep each platform / theme block to top 5, no pagination, no link dumps.

Edge cases

  • get_latest_news returns empty / very stale. Call mcp__trendradar__get_system_status to check crawl freshness. If the latest crawl is clearly stale, fall back to mcp__trendradar__get_latest_rss and tell the user the snapshot is from RSS feeds, not the platform crawl. Don't silently substitute.
  • User asks for a platform not in the supported list. Supported set: zhihu, weibo, douyin, bilibili, toutiao, baidu, thepaper, ifeng, tieba, cls-hot, wallstreetcn-hot. If they ask for something else (e.g. xiaohongshu, twitter), say so explicitly, list what is available, and ask whether to proceed with the closest covered platforms.
  • One of the two extraction calls fails. Render the output with whatever succeeded and note which bucket (preset / emergent) is missing. Don't block the whole response on a single failure.
  • User asks for a date in the past. Resolve via mcp__trendradar__resolve_date_range, then use mcp__trendradar__get_news_by_date instead of get_latest_news. Same extraction + cross-reference flow afterwards.
  • Ambiguous "今天" near midnight. Trust get_latest_news — it returns the most recent crawl batch regardless of wall-clock date.

Don'ts

  • Don't paginate huge lists. Cap at top 5 per platform / per theme. The user wants a snapshot, not a dump.
  • Don't include URLs unless the user explicitly asked for them. include_url=False is the default for a reason — links blow up the output.
  • Don't fabricate trend data when MCP fails. If get_latest_news errors out and the RSS fallback also fails, say so plainly and stop — never invent platform rankings.
  • Don't merge preset-keyword and auto-extract output into one undifferentiated list. The 全网共振 / 新冒头 split is the whole point of running both extraction modes.
  • Don't issue the two get_trending_topics calls sequentially. They are independent — fire them in parallel.

See also

  • ../docs/mcp-tools.md — full mcp__trendradar__* tool catalog (parameters, return shapes, rate-limit notes).

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.