Han River Water Level
Let your coding agent answer live Han River bridge water level and flow questions in Korean without you provisioning an HRFCO ServiceKey.
Overview
Han River Water Level is an agent skill for the Operate phase that fetches current Han River observatory water level and flow via the k-skill-proxy and returns a compact Korean-friendly summary.
Install
npx skills add https://github.com/nomadamas/k-skill --skill han-river-water-levelWhat is this skill?
- Calls the default k-skill-proxy `v1/han-river/water-level` endpoint over HTTP—no extra client SDK layer required
- Accepts `stationName` (bridge/station label) or `stationCode` (e.g. 1018683) with optional `KSKILL_PROXY_BASE_URL` overr
- Upstream HRFCO ServiceKey stays on the proxy; solo builders never inject secrets in the agent session
- Returns a compact summary: station name/code, observation time, level (m), flow (m³/s), and any present alert thresholds
- Handles ambiguous names via `ambiguous_station` plus `candidate_stations` so the agent can re-query with a precise stati
- Default proxy path: `https://k-skill-proxy.nomadamas.org/v1/han-river/water-level`
- Documented example stationCode: `1018683`
- Compact answer covers up to five threshold tiers when present: 관심/주의/경보/심각
Adoption & trust: 2.3k installs on skills.sh; 5.4k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You want live 한강 수위·유량 for a named bridge or station code but do not want to manage HRFCO API keys or a custom upstream client in your agent.
Who is it for?
Korea-based solo builders, safety or civic side projects, and agents that answer ad-hoc “지금 수위 어때?” questions during operations or field checks.
Skip if: Builders outside Korea who need non–Han-River hydrology, long historical series, or offline flood modeling without the nomadamas proxy.
When should I use this skill?
User asks for current Han River water level or flow by bridge/station name (e.g. 한강대교, 잠수교) or by observatory code such as 1018683.
What do I get? / Deliverables
The agent issues one proxy GET with stationName or stationCode and reports observation time, level, flow, and applicable threshold levels—or asks you to choose among candidate_stations when the name is ambiguous.
- Compact summary: station name/code, observation time, level (m), flow (m³/s), and present threshold references
- Disambiguation prompt listing candidate_stations when the proxy returns ambiguous_station
Recommended Skills
Journey fit
The skill’s only job is fetching and summarizing current observatory readings for operational awareness, not building features or launching growth work. Outputs are real-time level, flow, observation time, and threshold status—classic production monitoring signals for flood-related checks.
How it compares
Use this curated proxy-backed skill instead of wiring the raw HRFCO flood API and ServiceKey handling yourself in every chat session.
Common Questions / FAQ
Who is han-river-water-level for?
It is for solo and indie builders (and their agents) who work in Korean and need quick, current Han River water level and discharge at a known bridge name or observatory code.
When should I use han-river-water-level?
Use it during Operate monitoring when someone asks for live readings—e.g. 한강대교 수위, 잠수교 유량, or a direct stationCode lookup—before committing to dashboards or alerting automation.
Is han-river-water-level safe to install?
The skill only documents HTTP calls to a third-party proxy; review the Security Audits panel on this Prism page and treat the proxy as an external dependency you trust with query parameters and response data.
SKILL.md
READMESKILL.md - Han River Water Level
# Han River Water Level ## What this skill does 기본적으로 `https://k-skill-proxy.nomadamas.org/v1/han-river/water-level` 로 요청해서 현재 수위와 유량을 요약한다. ## When to use - "한강대교 지금 수위 어때?" - "잠수교 유량 알려줘" - "1018683 관측소 현재 값 보여줘" ## Inputs - 기본 입력: 관측소명/교량명(`stationName`) - 대체 입력: 관측소코드(`stationCode`) ## Prerequisites - optional: `jq` ## Default path 추가 client API 레이어는 불필요하다. 그냥 프록시 서버에 HTTP 요청만 넣으면 된다. 사용자는 별도 HRFCO `ServiceKey` 를 준비할 필요가 없다. upstream key는 proxy 서버에서만 주입한다. `KSKILL_PROXY_BASE_URL` 환경변수가 있으면 그 값을 사용하고, 없으면 기본 경로 `https://k-skill-proxy.nomadamas.org` 를 사용한다. ## Example requests ```bash curl -fsS --get 'https://k-skill-proxy.nomadamas.org/v1/han-river/water-level' \ --data-urlencode 'stationName=한강대교' ``` 관측소코드로 바로 조회해도 된다. ```bash curl -fsS --get 'https://k-skill-proxy.nomadamas.org/v1/han-river/water-level' \ --data-urlencode 'stationCode=1018683' ``` ## Keep the answer compact 응답에는 아래만 먼저 정리한다. - 관측소명 / 관측소코드 - 관측 시각 - 현재 수위(m) - 현재 유량(m^3/s) - 기준 수위(관심/주의/경보/심각) 중 값이 있는 항목 ## Ambiguous station names 입력이 너무 넓으면 proxy 는 `ambiguous_station` 과 함께 `candidate_stations` 를 돌려준다. ```bash curl -fsS --get 'https://k-skill-proxy.nomadamas.org/v1/han-river/water-level' \ --data-urlencode 'stationName=한강' ``` 이때는 후보 중 하나를 골라 다시 `stationName` 또는 `stationCode` 로 조회한다. ## Detailed API paths 구현 세부는 아래 문서만 참고한다. - `docs/features/han-river-water-level.md` - `docs/features/k-skill-proxy.md` ## Failure modes - 관측소명이 너무 넓어서 여러 관측소가 동시에 잡히는 경우 - 잘못된 관측소코드/관측소명으로 station lookup 이 실패하는 경우 - 프록시 서버에 `HRFCO_OPEN_API_KEY` 가 비어 있는 경우 - 실시간 자료 갱신 지연으로 최신 10분 자료가 비어 있는 경우 ## Notes - 기본 경로는 항상 `k-skill-proxy.nomadamas.org` 의 water-level endpoint 다. - upstream 은 `waterlevel/info.json` 으로 관측소 메타데이터를 찾고, `waterlevel/list/10M/{WLOBSCD}.json` 으로 최신값을 조회한다. - 결과는 원시자료 기반이므로 조회 시각을 함께 적는다.