界面已本地化;技能介绍与说明文档按所选语言由 AI 自动翻译,代码、命令、路径和专业术语保留原文,以原作者文档为准。
探索技能
效率与协作 · SKILL.md

crisis-monitor

crisis-monitor

【效率与协作】Rapidly assess crisis situations by monitoring Twitter, Reddit, news, and Chinese social platforms simultaneously. Detects escalation velocity, identifies key narratives, tracks official responses, and measures public sentiment shifts during critical events.

独立 GitHub 快照 · 自动分类 · 以原作者文档为准

技能说明

GitHub

name: crisis-monitor description: "Rapidly assess crisis situations by monitoring Twitter, Reddit, news, and Chinese social platforms simultaneously. Detects escalation velocity, identifies key narratives, tracks official responses, and measures public sentiment shifts during critical events."

Crisis Monitor

Rapidly assess crisis situations by monitoring Twitter, Reddit, news, and Chinese social platforms simultaneously. Detects escalation velocity, identifies key narratives, tracks official responses, and measures public sentiment shifts during critical events. 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_search_timeline
  • twitter_web_trending
  • reddit_app_dynamic_search
  • google_news_bulk_articles
  • weibo_web_hot_search
  • weibo_web_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.
我的收藏