executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
crisis-monitorRapidly 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.
Independent GitHub snapshot · Automated classification · Original documentation governs
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.
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.
twitter_web_search_timelinetwitter_web_trendingreddit_app_dynamic_searchgoogle_news_bulk_articlesweibo_web_hot_searchweibo_web_searchsandbase_discover, then inspect the returned name with sandbase_inspect to confirm the schema and pricing.execute_as with sandbase_run; collect async results with sandbase_run_get as described above.sandbase_inspect before using any capability.