Monitor cross-platform trends and alert agents with TrendRadar
Use TrendRadar when an operator needs a self-hosted trend monitor that filters multi-platform feeds, summarizes signals with AI, sends alerts, and exposes trend analysis through MCP.
npx skills add agentskillexchange/skills --skill monitor-cross-platform-trends-and-alert-agents-with-trendradar
TrendRadar is a self-hosted public-opinion and trend monitoring workflow for operators who need an agent-readable signal feed instead of another manual dashboard. The operator configures source channels, RSS feeds, keywords, delivery targets, and AI filtering rules, then lets TrendRadar collect hot topics, reduce noise, translate or summarize items, and push compact alerts to channels such as Slack, Telegram, email, ntfy, Bark, WeChat, Feishu, or DingTalk.
What this skill actually does
Use this skill when a user asks an agent to watch changing news, product, community, or market topics across several sources and bring back only the items that match a reviewable watchlist. The agent should treat TrendRadar as the collection and filtering surface, inspect the configured sources and alert rules, ask TrendRadar or its MCP surface for relevant trend context, and return a concise brief with links, timestamps, source names, and the filter logic used.
This is not a generic social-monitoring product card. The scope boundary is the repeatable operator workflow around self-hosted TrendRadar: deploy the service, configure watched sources and keywords, keep notification targets explicit, use AI filtering or summaries where configured, and expose the trend data to MCP-capable assistants for sentiment, topic, and trend analysis. Do not use it as a license to publish posts or send public responses automatically; alerts and briefs should remain reviewable before any outbound action.
Inputs and prerequisites: Docker or Python deployment, TrendRadar configuration, source/RSS credentials where needed, notification channel credentials, optional model credentials, and an MCP-capable client when agent query access is required.
Setup notes: Follow the upstream documentation to deploy TrendRadar, configure feeds and keywords, enable desired notification channels, and enable the MCP integration only for the agent clients that should query the trend monitor.
Source and verification boundary: use https://github.com/sansan0/TrendRadar and https://sansan0.github.io/TrendRadar/ as the canonical references before running the workflow; keep source lists, alert rules, MCP calls, and generated briefs auditable against that upstream source.