Situation Monitor
Use this skill when the user wants to catch up on Discord traffic, monitor a
few noisy channels, triage Kubernetes incidents, produce a digest, or draft a
safe follow-up.
Use the helper wrapper at scripts/mts for all commands. It bootstraps .venv
and installs the package on first run, which makes hosted OpenClaw installs far
more reliable than calling python3 -m monitoring_the_situation.cli directly.
Guardrails
- - Never use a user token or self-bot. Live mode requires a Discord bot token.
- Prefer fixture mode when a live Discord bot is not configured yet.
- Do not ingest personal or private account history for demos.
- Prefer public status pages, public incident feeds, and synthetic cluster
incidents for KubeWatch unless the user explicitly provides other sources.
- - Treat outbound posting as sensitive. Drafts are allowed; sending stays blocked
until Civic approval is configured.
Working modes
- 1. Discord fixture mode for a safe demo:
CODEBLOCK0
- 2. Live Discord snapshot mode after bot setup:
CODEBLOCK1
- 3. Draft a reply for a specific report item:
CODEBLOCK2
- 4. KubeWatch fixture mode for the SRE lane:
CODEBLOCK3
- 5. KubeWatch live intake from Apify after sponsor setup:
CODEBLOCK4
- 6. KubeWatch live cluster scan against the demo namespace:
CODEBLOCK5
- 7. Rebuild and sanity-check the Apify actor when the repo changes:
CODEBLOCK6
The actor lives at the repo root, so Apify should stay pointed at the root with
no folder override.
Expected output
Produce a report with:
- - An executive summary
- Urgent threads
- Direct asks
- Decisions and deadlines
- FYI items
- Source citations by channel/message
- Incident priorities and grounded remediation steps for KubeWatch
If the user asks to send a message instead of drafting one, explain that the
repo is intentionally fail-closed until Civic-backed approvals are wired.
情境监控器
当用户希望了解Discord动态、监控几个嘈杂频道、分类处理Kubernetes事件、生成摘要或起草安全的后续跟进时,请使用此技能。
所有命令均使用scripts/mts下的辅助包装器。它会在首次运行时引导.venv并安装软件包,这使得托管式OpenClaw安装比直接调用python3 -m monitoringthesituation.cli更可靠。
防护措施
- - 切勿使用用户令牌或自建机器人。实时模式需要Discord机器人令牌。
- 在尚未配置实时Discord机器人时,优先使用固定数据模式。
- 请勿为演示目的摄取个人或私人账户历史记录。
- 除非用户明确提供其他来源,否则KubeWatch应优先使用公共状态页面、公共事件源和合成集群事件。
- 将对外发布视为敏感操作。允许起草;在配置Civic审批之前,发送功能保持禁用状态。
工作模式
- 1. 用于安全演示的Discord固定数据模式:
bash
bash scripts/mts fixture \
--input examples/demo_messages.json \
--save-path .local/demo_report.md
- 2. 机器人设置完成后的实时Discord快照模式:
bash
bash scripts/mts discord-fetch \
--hours 24 \
--limit-per-channel 75 \
--save-path .local/live_report.md
- 3. 为特定报告条目起草回复:
bash
bash scripts/mts draft-reply \
--bucket urgent \
--channel api-alerts
- 4. 用于SRE通道的KubeWatch固定数据模式:
bash
bash scripts/mts kubewatch-fixture \
--input examples/kubewatch_incidents.json \
--save-path .local/kubewatch_report.md
- 5. 赞助商设置完成后从Apify实时获取KubeWatch数据:
bash
bash scripts/mts kubewatch-apify \
--actor-id $APIFYACTORID \
--actor-input examples/apifyactorinput.json \
--save-path .local/kubewatchlivereport.md
- 6. 针对演示命名空间的KubeWatch实时集群扫描:
bash
bash scripts/mts kubewatch-cluster \
--namespace production \
--save-path .local/kubewatchclusterreport.md
- 7. 当仓库发生变化时重建并检查Apify actor的完整性:
bash
cd /Users/sarahhatcher/Documents/monitoring-the-situation-openclaw
npm install
node main.js
Actor位于仓库根目录,因此Apify应保持指向根目录,无需文件夹覆盖。
预期输出
生成包含以下内容的报告:
- - 执行摘要
- 紧急线程
- 直接请求
- 决策与截止日期
- 仅供参考事项
- 按频道/消息标注的来源引用
- KubeWatch的事件优先级和基于事实的修复步骤
如果用户要求发送消息而非起草消息,请说明该仓库有意设置为故障关闭状态,直到Civic支持的审批机制接入为止。