agentleFS
lorenliu13lorenliu13/claude-code-for-hydrology/.claude/skills/hydro-context/SKILL.md

hydro-context

Skill67 starsChanged 6 months agoMITView on GitHub

Apply US hydrology domain knowledge — units, formulas, and conventions — when reading or writing hydrological code

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Always check that input/output units are consistent.

    line 11

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

You are assisting with US hydrology / water resources engineering code. Apply the following domain knowledge automatically without asking the user to re-explain it.

Units

  • Discharge (streamflow): cubic feet per second (cfs) in US datasets; m³/s (cms) internationally
  • Stage (water level): feet in USGS data; metres in international datasets
  • Always check that input/output units are consistent; flag mismatches as a comment or warning

Key formulas

Rating curve (stage-discharge): Q = a × (H – H₀)^b

  • H = stage, H₀ = zero-flow stage offset, a and b are fitted constants
  • Typical b range: 1.5–3.0 for natural channels; fit in log-log space

Manning's equation (open-channel flow): Q = (1/n) × A × R^(2/3) × S^(1/2)

  • n = Manning's roughness (0.025–0.05 for natural channels)
  • R = hydraulic radius, S = channel slope (dimensionless, m/m or ft/ft)

Log-Pearson Type III is the standard US flood frequency distribution (USGS Bulletin 17C).

  • Work in log₁₀ space: fit the mean, standard deviation, and skewness of log₁₀(Q)

Weibull plotting position: P(X ≤ x) = m / (n + 1), return period T = (n + 1) / m

  • m = rank (1 = smallest), n = total number of data points

Flood frequency terminology

  • Return period (recurrence interval): average years between events of that magnitude or greater
  • Q2: 2-year flood (50% annual exceedance probability) ≈ bankfull flow in many streams
  • Q10: 10-year flood (10% AEP)
  • Q100: 100-year flood (1% AEP) — US regulatory floodplain standard
  • AEP: Annual Exceedance Probability = 1 / T

Data quality conventions

  • USGS missing-data sentinel: -999999 — always filter these before any calculation
  • Negative discharge values are physically impossible — treat as errors
  • Water year: Oct 1 – Sep 30 (US convention); water year N starts Oct 1 of year N-1
  • Minimum record length for reliable flood frequency: ≥ 10 years (30+ preferred for Q100)

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.