War-risk monitoring focuses on the Korean Peninsula and its surrounding region.
한반도·대만 전쟁 위험을 예측 지표로 매시간 점수화하고, 의미 있는 변화만 알리며 하루 두 번 X용 보고서 초안을 만들어 주는 봇이에요.
Query this catalog from Claude, Cursor, or Grok via MCP.
Memories16Facts it already knows
Prioritize predictive indicators and exclude reactive ones like earthquake/seismic data and news volume counts, but include Google Trends search data as a public-sentiment indicator.
Benchmark the war-risk score against a peaceful-period baseline rather than a recent rolling average, so sustained high tension keeps scoring high until it resolves.
Jointly model China-invading-Taiwan and North-Korea-invading-South-Korea risks as organically coupled (each raising the other), not as separate add-ons.
Monitor China's situation (PLA activity around Taiwan/Yellow Sea, China-related markets) together with North Korea in the score and reports.
Include Polymarket prediction-market data in monitoring and reports, clearly labelled.
Comprehensively include all relevant North Korea/DMZ incidents (mine laying, mine explosions, fence-cutting attempts, MDL incursions) in the score, with none omitted or hidden by merging.
Limit event labels on the 90-day graph to significant events; minor ones are left off the chart but still count in the score.
Chart shows only the gauge and the 90-day graph, rendered high resolution (2160px wide, enlarged text) so it stays readable after X compression.
Prepare war-risk report drafts twice a day, at 7 AM and 6 PM local time.
Reports are short plain text formatted to fit X, focused on what changed since the last report.
Short-term changes compare against the immediately preceding report (about 12 hours earlier), not a day earlier, while still covering long-term trends versus 7 and 30 days earlier; never repeat items already in the previous report.
Include viral rumors and warnings circulating online, with whether each one is verified.
Save each report (text with its chart image) to the owner's X drafts folder; never publish.
Hourly alerts that change band are also saved as X drafts with the chart, never published.
Don't alert or draft for small wobbles around a band line (e.g., 59↔62); only band crossings of 3+ points past the line with a real driver count.
Skills1Playbooks it can run
war-alarm-getting-started
Use as the first conversation of an imported Korean-peninsula war-risk alarm bot, to set it up with its new owner.
Routines2Jobs that run on their own
한반도 전쟁 조기경보 시간별 체크
Every hour, score war risk and alert only on meaningful changes.
한반도 전쟁 위험 보고서 (07시·18시)
Twice a day, write a short X-ready war-risk report and save it as an X draft.
You may also like
Optimus by Efficient
by Efficient
Commander for a multi-bot team. Runs morning motivation + activity briefs, weekday roll-calls, and an evening growth-campaign pulse while coordinating scout, d…
- Memories5
- Skills0
- Routines3
X Growth Coach
by Ivan kim
Your personal growth coach for X. Every morning it shows how your analytics changed since yesterday, sends a weekly trend review, and scores your drafts agains…
- Memories12
- Skills3
- Routines1
Executive Assistant
by Raphael
Runs your day: a weekday morning brief, inbox triage with draft replies, meeting prep, calendar defence, travel and occasions. Never sends, books or moves anyt…
- Memories2
- Skills1
- Routines2
BCDR Benny
by Red
BCDR steward for multi-bot Grok Bot teams: durable-store habits, end-of-job checks, a recovery ladder, an optional memory mirror, and weekday gap reminders so…
- Memories0
- Skills4
- Routines1
SwarmCoordinator Bot
by Chase McCarty
A project manager for a swarm of bots. It keeps each project's backlog on a Notion board, hands each bot one card at a time, writes and enforces the team's run…
- Memories5
- Skills4
- Routines0



