Token导航 LogoToken导航TokenDH.com
研究检索需要联网github未标认证来源可访问许可证需确认审计提醒

hormuz-strait霍尔木兹海峡

Agent Skill

hormuz-strait 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

9,382

周安装

403

GitHub Stars

1,399

下载量

3,288
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:hormuz-strait(霍尔木兹海峡)
来源仓库:https://github.com/himself65/finance-skills
仓库路径:skills/hormuz-strait
安装命令:
npx skills add https://github.com/himself65/finance-skills --skill hormuz-strait
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/himself65/finance-skills --skill hormuz-strait

简介

用于根据关键词或线索快速查找、检索和筛选相关信息。

  • 适用于需要从大量数据中定位候选结果的研究或开发场景。
  • 通过 npx skills add 命令从指定 GitHub 仓库安装。
  • 支持 Codex、Claude、Cursor、Gemini CLI,安装方式为 github。
  • hormuz-strait 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

Hormuz Strait Monitor Skill

Fetches real-time status of the Strait of Hormuz from the Hormuz Strait Monitor dashboard API. Covers shipping transits, oil prices, stranded vessels, insurance risk, diplomatic status, global trade impact, and crisis timeline.

This skill is read-only. It fetches public dashboard data — no authentication required.


Step 1: Fetch Dashboard Data

Use curl to fetch the dashboard API:

curl -s https://hormuzstraitmonitor.com/api/dashboard

Parse the JSON response. The API returns {"success": true, "data": {...}, "timestamp": "..."}.

If success is false or the request fails, inform the user the monitor is temporarily unavailable and suggest checking https://hormuzstraitmonitor.com directly.


Step 2: Identify What the User Needs

Match the user's request to the relevant data sections. If the user asks for a general status update, present all sections. If they ask about something specific, focus on the relevant section(s).

User RequestData SectionKey Fields
General status / "is Hormuz open?"straitStatusstatus, since, description
Ship traffic / transit countshipCountcurrentTransits, last24h, normalDaily, percentOfNormal
Oil price impactoilPricebrentPrice, change24h, changePercent24h, sparkline
Stranded / stuck vesselsstrandedVesselstotal, tankers, bulk, other, changeToday
Insurance / war riskinsurancelevel, warRiskPercent, normalPercent, multiplier
Cargo throughputthroughputtodayDWT, averageDWT, percentOfNormal, last7Days
Diplomatic situationdiplomacystatus, headline, parties, summary
Global trade impactglobalTradeImpactpercentOfWorldOilAtRisk, estimatedDailyCostBillions, affectedRegions, lngImpact, alternativeRoutes, supplyChainImpact
Crisis timeline / eventscrisisTimelineevents[] with date, type, title, description
Tanker freight rates / VLCC ratestankerRatescurrentRate, preCrisisRate, changePercent, route, vesselType, trend, unit
Latest newsnewstitle, source, url, publishedAt, description

Step 3: Present the Data

Format the results clearly for financial research. Adapt the presentation based on what the user asked for.

General status briefing (default)

When the user asks for a general update, present a concise briefing covering all key sections:

  1. Strait Status — lead with the current status (e.g., "OPEN", "RESTRICTED", "CLOSED"), how long it's been in that state, and the description
  2. Ship Traffic — current transits, last 24h count, and percent of normal
  3. Oil Price — Brent price with 24h change
  4. Stranded Vessels — total count broken down by type, with today's change
  5. Insurance Risk — risk level, war risk premium percentage, and multiplier vs. normal
  6. Cargo Throughput — today's DWT vs. average, percent of normal
  7. Diplomatic Status — current status, headline, and brief summary
  8. Global Trade Impact — percent of world oil at risk, estimated daily cost, and top affected regions
  9. Tanker Freight Rates — current VLCC rate on the benchmark route vs. pre-crisis baseline, with trend direction

Formatting guidelines

  • Use tables for structured data (vessel counts, affected regions, alternative routes)
  • Highlight abnormal values — if percentOfNormal is below 80% or above 120%, call it out
  • For oilPrice.sparkline, describe the trend (rising, falling, stable) rather than listing raw numbers
  • For throughput.last7Days, describe the trend direction
  • Show lastUpdated timestamp so the user knows data freshness
  • For news items, include the source and link
  • For crisis timeline events, present chronologically with event type labels

Risk assessment

Based on the data, provide a brief risk assessment:

Values are returned uppercase.

Insurance LevelInterpretation
NORMALNo elevated risk — shipping operating normally
ELEVATEDSome disruption concerns — monitor closely
HIGHSignificant risk — active disruption or credible threat
CRITICALSevere disruption — major impact on global oil supply
EXTREMEEffective closure — war risk premiums at multi-decade highs, most commercial traffic halted

If the strait status is anything other than fully open, highlight:

  • The estimated daily cost to global trade
  • Which regions are most affected and their oil dependency
  • Available alternative routes with additional transit days and cost
  • LNG impact if applicable
  • SPR (Strategic Petroleum Reserve) status in days

Step 4: Respond to the User

  • Lead with the most important information: strait status and any active disruption
  • Include data freshness (lastUpdated timestamp)
  • If the situation is elevated or worse, proactively include the global trade impact summary
  • Keep the response concise for routine "all clear" statuses; expand for active incidents
  • Add a disclaimer: data is sourced from Hormuz Strait Monitor and may have delays

Reference Files

  • references/api_schema.md — Complete API response schema with field descriptions and data types

Read the reference file when you need exact field names or data type details.

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

34.76%
按下载量换算1,143

Claude

28.76%
按下载量换算946

Cursor

17.66%
按下载量换算581

Gemini CLI

9.18%
按下载量换算302

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills