← ClaudeAtlas

swmm-end-to-endlisted

Top-level orchestration skill for agentic SWMM modelling. Use when an agent needs one entrypoint that decides which module tools to run, in what order, and when to stop, for example to build, run, QA, and optionally calibrate a SWMM case from prepared or partially prepared inputs.
Zhonghao1995/agentic-swmm-workflow · ★ 27 · AI & Automation · score 77
Install: claude install-skill Zhonghao1995/agentic-swmm-workflow
# SWMM End-to-End Orchestration Part of [Agentic SWMM](https://github.com/Zhonghao1995/agentic-swmm-workflow) — install the project first for the executable toolchain (aiswmm CLI, SWMM solver, MCP servers). ## What this skill provides - A top-level orchestration contract for the agent runtime. - A stable handoff point for Agentic AI project memory in `agent/memory/`. - A deterministic execution order across the existing module skills: - `swmm-canada` (entry skill for Canadian AOIs — real municipal pipes where covered, synthesized elsewhere in Canada) - `swmm-anywhere` (entry skill for data-scarce regions outside Canada — no real pipe data) - `swmm-gis` - `swmm-climate` - `swmm-params` - `swmm-network` - `swmm-builder` - `swmm-runner` - `swmm-design-review` - `swmm-plot` - `swmm-calibration` - `swmm-uncertainty` - `swmm-lid-optimization` - `swmm-experiment-audit` ## Routing rule — real-data path vs synth-data path The orchestrator MUST inspect the user's inputs before choosing the entry skill: - If the request includes any of `.shp`, `.csv`, `network.json`, a CAD file, or an existing `.inp` path → the user has real data; route to `swmm-network` (or `swmm-builder` if the INP is already prepared). - If the request includes only a **bbox** or a **location name** with no pipe-network file attached → check the country first. For a **Canadian** AOI route to `swmm-canada` (the SWMMCanada upstream returns real published municipal storm pipes where a su