What problem does it solve? Running the TopoFlow 3.6 spatially-distributed hydrologic model requires operational expertise scattered across source code and docs: correct unit conversions (mm/hr vs m/s precipitation, K vs °C temperature), D8 grid preparation, component selection via provider files, and recovery from silent failures. This Skill packages that expertise so an AI agent can configure, execute, and validate real TopoFlow runs without substituting approximations. ## Core Features & Use Cases - Forcing and soil data conversion: Tools convert ERA5/CMFD/MSWX reanalysis and HWSD/SoilGrids data into TopoFlow's expected formats with correct units, catching common traps like Kelvin temperatures or mm/hr hydraulic conductivity. - Model execution and output parsing: Run the EMELI-coupled model via run_topoflow.py and extract outlet hydrographs, grid stacks, and metrics (NSE, KGE, PBIAS) with parse_output.py. - Diagnostic recovery: 18 symptom-to-remedy triplets in diagnostics/triplets.yaml map known failure modes (unit errors, CFL violations, provider typos) to validated fixes. - Use Case: Simulate the June 1967 rainfall events over the Treynor, Iowa watershed, then score the simulated outlet discharge hydrograph against observed streamflow using cited NSE/PBIAS validation bands. ## Quick Start Ask the agent to run the preflight check and then execute the TopoFlow Treynor Iowa example, converting ERA5 forcing for the basin and validating the outlet discharge against observed data.