Evo Usgs Flood Detection logo

Evo Usgs Flood Detection

Organization
OpenLAIR
evo-usgs-flood-detection

Detects flooding events at USGS streamgages by comparing daily streamflow against historical 90th percentile thresholds using the dataretrieval package. Use when analyzing flood occurrences over a date range for a list of USGS station IDs.

Overview

PublisherOpenLAIR
RepositoryOpenSkill
Skill nameevo-usgs-flood-detection
Stars
97
Forks
4
Bundled files
2
LicenseApache-2.0
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 2 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by OpenLAIR on GitHub. Read the source before you install it.

Installation

Install the Evo Usgs Flood Detection AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/OpenLAIR/OpenSkill/tree/main/tasks-evolved/flood-risk-analysis/environment/skills/evo-usgs-flood-detection
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/OpenLAIR/OpenSkill.git /tmp/OpenSkill
mkdir -p .claude/skills
cp -r /tmp/OpenSkill/tasks-evolved/flood-risk-analysis/environment/skills/evo-usgs-flood-detection .claude/skills/evo-usgs-flood-detection
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Evo Usgs Flood Detection in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Evo Usgs Flood Detection on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Evo Usgs Flood Detection is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

evo-usgs-flood-detection

Overview

End-to-end pipeline for detecting flooding at USGS streamgages. Reads station IDs from a file, fetches daily streamflow values and historical statistics via dataretrieval.nwis, computes flood-day counts by comparing observed daily mean streamflow against the 90th percentile historical threshold for each calendar day, and writes filtered results to CSV.

Key Concepts

Flood Definition

A flood day is defined as a day where the observed daily mean streamflow (00060_Mean) exceeds the 90th percentile (p90_va) of historical daily mean streamflow for that same calendar day (month + day).

Data Sources

  • Daily Values: nwis.get_dv(sites, parameterCd='00060', start, end) → returns (DataFrame, metadata) tuple
  • Historical Stats: nwis.get_stats(sites, statReportType='daily', parameterCd='00060') → returns (DataFrame, metadata) tuple with columns month_nu, day_nu, p90_va

Station ID Handling

USGS station IDs have leading zeros (e.g., 04193500). Always read as strings, never as integers.

Functions

load_stations(filepath: str) -> List[str]

Reads station IDs from a flat text file (one per line) or CSV with station_id header. Preserves leading zeros.

get_station_flood_thresholds(site_id: str) -> pd.DataFrame

Fetches 90th percentile historical daily streamflow thresholds. Returns DataFrame with month_nu, day_nu, p90_va.

detect_floods_for_site(site_id: str, start_date: str, end_date: str) -> int

Fetches daily values, merges with thresholds on month/day, counts days where observed > p90. Returns integer count.

run_flood_detection_pipeline(stations_file, out_file, start, end) -> pd.DataFrame

Orchestrates the full pipeline. Processes all stations, filters to those with >=1 flood day, writes CSV.

Usage

python
import sys
sys.path.insert(0, '/app/environment/skills/evo-usgs-flood-detection/scripts')
from utils import load_stations, detect_floods_for_site, run_flood_detection_pipeline

# Run full pipeline
results = run_flood_detection_pipeline(
    stations_file='/root/data/michigan_stations.txt',
    out_file='/root/output/flood_results.csv',
    start='2025-04-01',
    end='2025-04-07'
)

Output Format

CSV with two columns:

  • station_id: 8-digit USGS station ID (string with leading zeros)
  • flood_days: Number of days with flooding (positive integer, max 7 for a 7-day window)

Only stations with at least 1 flood day are included.

Dependencies

  • dataretrieval 1.0.10
  • pandas 2.2.3
  • Python 3.x

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Evo Usgs Flood Detection AI skill do?

Detects flooding events at USGS streamgages by comparing daily streamflow against historical 90th percentile thresholds using the dataretrieval package. Use when analyzing flood occurrences over a date range for a list of USGS station IDs.

Why use Evo Usgs Flood Detection on TypingMind?

Because you install it once and use it with any model. Evo Usgs Flood Detection is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Evo Usgs Flood Detection in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/OpenLAIR/OpenSkill/tree/main/tasks-evolved/flood-risk-analysis/environment/skills/evo-usgs-flood-detection. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Evo Usgs Flood Detection?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Evo Usgs Flood Detection?

As many as you like. As long as a model supports skills, you can use Evo Usgs Flood Detection with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Evo Usgs Flood Detection AI skill free?

Yes. It is published on GitHub by OpenLAIR under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇