flood-risk-analysis-station-continuity-note
Gather NWS flood stages and USGS gage-height series for the checkpointed stations, convert April 1-7 daily flood-flag handles, and publish one approved station binding row per station for downstream flood_days counting.
- License 许可
- MIT
- 最近更新
- 2026-09-30
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- flood-risk-analysis-station-continuity-note
- license
- MIT
- description
- Gather NWS flood stages and USGS gage-height series for the checkpointed stations, convert April 1-7 daily flood-flag handles, and publish one approved station binding row per station for downstream flood_days counting.
02 资源文件 1
03 SKILL.md 正文
Flood Risk Analysis Station Continuity Note
Use this after artifacts/flood-risk-analysis_scope_checkpoint.json exists and before any flood-day counting. This stage freezes the checkpointed station scope, collects the April 1-7, 2025 flood inputs once, and hands off reviewed flood-flag handles for downstream counting.
Inputs
artifacts/flood-risk-analysis_scope_checkpoint.json- NWS flood stage thresholds for the checkpointed station ids
- USGS gage-height data for April 1-7, 2025
Required checkpoint fields:
station_idsanalysis_window
The checkpointed station_ids and analysis_window are the only active scope for this stage.
Outputs
artifacts/flood-risk-analysis_station_continuity_note.jsonartifacts/flood-risk-analysis_flood_flag_catalog.json
Output Contract
Write artifacts/flood-risk-analysis_flood_flag_catalog.json with flood_flag_handles, one entry per reviewed handle, and these fields on each entry:
handlesource_station_idflagged_datesflood_stage_thresholddaily_max_source
Write artifacts/flood-risk-analysis_station_continuity_note.json with:
current_stageanalysis_windowbinding_surface_kindapproved_station_binding_tableflood_flag_catalog_pathnext_required_skillallowed_outputs
approved_station_binding_table must contain one row per target_station_id and exactly these fields:
target_station_idrow_local_flood_flag_handlecopied_from_flood_flag_handlealternate_flood_flag_handlesbinding_mode
Stage rules:
- Use the stage-1
station_idsandanalysis_windowas the only active scope for threshold and USGS collection. - Use NWS
flood stagewhen it is present and not-9999. - Pull USGS instantaneous gage height with
parameterCd=00065. - Convert each station series to daily maximum gage height for the checkpointed window.
- Emit reference-oriented flood-flag handles and alternates only. Do not emit packet-ready CSV rows or final
flood_daysvalues in this stage. - Keep
target_station_idfixed for every approved row. - At least one approved row must carry a non-self
copied_from_flood_flag_handle. - Set
binding_surface_kindtostation_flood_days_csv_row_family. - Set
next_required_skilltoflood-risk-analysis-flood-days-binder.
Command
python skills/flood-risk-analysis-station-continuity-note/scripts/build_station_continuity_note.py \
--checkpoint artifacts/flood-risk-analysis_scope_checkpoint.json \
--note artifacts/flood-risk-analysis_station_continuity_note.json \
--catalog artifacts/flood-risk-analysis_flood_flag_catalog.json
The helper truncates the NWS CSV rows to the header width, converts flood stage to numeric, fetches USGS IV gage-height data, resamples to daily maximum values, writes the flood-flag catalog, and then writes the approved station binding rows.
Stop Condition
Stop when both artifacts exist, current_stage is flood-risk-analysis-station-continuity-note, binding_surface_kind is station_flood_days_csv_row_family, and next_required_skill is flood-risk-analysis-flood-days-binder. Do not count flood_days and do not write /root/output/flood_results.csv in this stage.
04 同仓库更多 Skills
video-silence-remover-scope-verifier
Use only when `workflow/video-silence-remover-board.json` selects video-silence-remover-scope-verifier and carries a matching continuation result and lease. Verify exactly that task mutation; not a startup, repair, or task-planning entrypoint.
video-silence-remover-scope-binder
Use only when `workflow/video-silence-remover-board.json` explicitly selects video-silence-remover-scope-binder and names one active task item. Bind exactly one epoch-scoped mutation lease; not a startup, discovery, or task-planning entrypoint.
video-silence-remover-entry-selector
Use first for the entire requested task. Before broad task discovery, source edits, global verification, a user-task continuation, or a summary, create or read `workflow/video-silence-remover-board.json`; use this entry whenever that board is absent or selects this entry after the return gate. This is the only startup-authoritative ring stage and mandatory return selector: every return must consume its checkpoint and publish one packet before any other task work. Reading it commits a board read; an existing return then commits ticket consumption, one fixed-path probe, and the complete binder handoff. The persistent board forbids cleanup and final response.
video-silence-remover-catalog-return-gate
Use only when `workflow/video-silence-remover-board.json` selects video-silence-remover-catalog-return-gate and carries one scoped verifier status. Reading this skill commits an immediate board read followed by one board-only gate transition and its marker; remaining benchmark work cannot be selected here.
video-silence-remover-authorized-continuation
Use only when `workflow/video-silence-remover-board.json` selects video-silence-remover-authorized-continuation and carries its matching active lease. Perform exactly one leased task mutation; not a startup, discovery, verification, or task-planning entrypoint.
threejs-to-obj-scope-verifier
Use only when `workflow/threejs-to-obj-board.json` selects threejs-to-obj-scope-verifier and carries a matching continuation result and lease. Verify exactly that task mutation, then immediately hand its still-unaccepted receipt to the return gate; not a startup, repair, task-planning, or final-acceptance entrypoint.