Agent Skills
› koala73/worldmonitor
› chokepoint-check
chokepoint-check
GitHub查询霍尔木兹、苏伊士等关键海运咽喉的船舶通行量、周环比变化及风险事件,用于评估航运中断或拥堵状况。
触发场景
询问海峡或运河是否中断
查询航运拥堵情况
检查特定咽喉要道的通行状态
安装
npx skills add koala73/worldmonitor --skill chokepoint-check -g -y
SKILL.md
Frontmatter
{
"name": "chokepoint-check",
"description": "Check shipping disruption at maritime chokepoints such as Hormuz, Suez, Bab el-Mandeb, Malacca and Panama - vessel transits today, week-over-week change, risk level and incidents - from World Monitor. Use when the user asks whether a strait or canal is disrupted, congested or safe for shipping."
}
Chokepoint check
Report the current state of one or all of the 13 maritime chokepoints World Monitor tracks.
Tools
| Tool | Access |
|---|---|
get_chokepoint_status |
free-account |
get_energy_intelligence |
free-account |
Steps
- Call
get_chokepoint_statuswithdataset: ["transit-summaries"]. Addchokepointwith a lowercase name fragment ("hormuz","suez","malacca","bab","panama") when the user names one. - For each chokepoint report today's transits (total, tanker and cargo), the week-over-week change, the risk level and incidents in the last seven days. The tool withholds the risk narrative (
riskSummaryis always empty); do not write one, and do not read the empty field as low risk. - When the user asks about oil or gas supply, also call
get_energy_intelligenceand add active disruptions that mention the chokepoint.
Rules
- Transit counts come from vessel position data and are flagged stale after 30 minutes. State the observation time, and say so plainly when the data is stale or
dataAvailableis false. - Compare against the week-over-week figure in the data. Do not invent a historical baseline.
- Do not give routing, insurance or trading advice.
版本历史
- 11e2bc8 当前 2026-11-03 09:06


