UI はローカライズ済みです。スキルの紹介と説明文書は選択した言語へ AI が自動翻訳し、コード・コマンド・パス・専門用語は原文のままです。原作者の文書が優先されます。
スキルを探す
生産性・共同作業 · SKILL.md

trend-spotter

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.

Independent GitHub snapshot · Automated classification · Original documentation governs

スキルの説明

GitHub

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 before selecting a capability.

Call SandBase capabilities

Use the capability identifiers below as discovery hints, not MCP tool names. Find the matching endpoint with sandbase_discover(q: "<provider and capability>"); use its returned name in sandbase_inspect(name: "<returned name>"). Read inputSchema, pricing, and execute_as, then call sandbase_run using execute_as.arguments.name and schema-defined arguments. If a run_id is returned, poll sandbase_run_get(run_id: "<returned run_id>") within the task budget until completed or failed; report pending or failed runs without resubmitting them automatically.

Capability identifiers

  • 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. Resolve each selected capability with sandbase_discover, then inspect the returned name with sandbase_inspect to confirm the schema and pricing.
  3. Follow execute_as with sandbase_run; collect async results with sandbase_run_get as described above.
  4. Synthesize findings into a clear, evidence-backed answer.
  5. Cite sources, note evidence gaps, and separate observations from interpretations.

Guidelines

  • Always call sandbase_inspect 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.
保存したスキル