trend-spotter · git:20260813.48597a3 · 2026-08-13 · sha256 ae36fd15fe25967e
trend-spotter git:20260813.48597a3A
Immutable. This exact content is served forever at /api/v1/blob/ae36fd15fe25967e.
--- name: trend-spotter description: "Identify emerging trends early by monitoring signals across Twitter trending, TikTok viral content, YouTube rising videos, Google News velocity, and Reddit community buzz. Combines platform-specific trend indicators into a unified trend confidence score." --- # Trend Spotter Identify emerging trends early by monitoring signals across Twitter trending, TikTok viral content, YouTube rising videos, Google News velocity, and Reddit community buzz. Combines platform-specific trend indicators into a unified trend confidence score. Read [the API map](references/sandbase-api-map.md) before selecting a capability. ## Call SandBase capabilities For every selected tool, call `sandbase_describe_tool` first and use only arguments in its current input schema. Then call `sandbase_call_tool` with the exact `tool_name`. ## Available Tools - `twitter_web_trending` - `tiktok_app_v3_home_feed` - `youtube_web_v2_general_search` - `google_news_bulk_articles` - `reddit_app_popular_feed` - `weibo_web_hot_search` ## Workflow 1. Understand the user's research question, target, and context. 2. Call `sandbase_describe_tool` for each selected tool to confirm parameter schema. 3. Call `sandbase_call_tool` with the exact tool_name and schema-defined arguments. 4. Synthesize findings into a clear, evidence-backed answer. 5. Cite sources, note evidence gaps, and separate observations from interpretations. ## Guidelines - Always call `sandbase_describe_tool` before using any capability. - Cite sources and preserve attribution (URLs, usernames, dates, metrics). - Separate factual observations from analysis and recommendations. - If data is unavailable, note the gap and continue with available evidence. - Read-only research only. Never take actions on platforms.