trend-alert

trend-alert

Anomaly detection on a watchlist of topics, with channel-correct push delivery via the trendradar MCP. Each spike is verified, formatted per channel, and rate-limited before being sent.

When to activate

Trigger when the user expresses any of:

• 异动告警 / 突发热点推送 / breakout alert
• 监控 XX 话题 / 订阅热点 / 盯盘 / 关注列表
• 推送到飞书 / 钉钉 / Telegram / Slack / Bark / 邮件 / ntfy / 企业微信 / webhook
• "ping me when X spikes" / "alert me if X breaks out" / "通知我 X 暴涨"

Do NOT activate for routine "show me trends" or recap requests — those belong to trend-monitor or trend-report.

Workflow

1. Resolve watchlist. Take topics from the user message. If they reference a stored list ("我的关注列表"), look in shared memory; otherwise ask once for the explicit topics. Normalize to a deduped list of strings.

2. Detect anomalies per topic. For each topic in the watchlist call:

   mcp__trendradar__analyze_topic_trend(
     topic="<topic>",
     analysis_type="viral",
     spike_threshold=3.0,
     time_window=24
   )
   

   Run these calls in parallel where possible.

3. Filter to real spikes. Keep only topics whose response indicates a genuine spike (e.g. is_spike=true, viral_score above threshold, or explicit spike_detected). Discard noise. If nothing spikes, tell the user "无异动" and stop — do NOT push an empty alert.

4. Discover configured channels.

   mcp__trendradar__get_notification_channels()
   

   Use the returned channels[] to know which ids have configured: true. If the user named a channel that is not configured, surface the missing env var keys (see Edge cases) and skip that channel.

5. Per channel: fetch format rules, format, send. For each target channel <id>:

   mcp__trendradar__get_channel_format_guide(channel="<id>")
   

   Use the guide.supported / guide.unsupported / guide.prompt fields to format the message body. Then:

   mcp__trendradar__send_notification(
     channel="<id>",
     title="【异动】<topic>",
     content="<formatted body>"
   )