open-meteo-flood-fetch
Fetch Open-Meteo Flood API daily river-discharge data for specified date windows and coordinates with retries, throttling, detailed logs, and transport/structure validation. Use when tasks need deterministic flood or runoff verification for ecology and environmental monitoring, such as checking river discharge background, flood risk windows, or ensemble-style discharge signals for one or more coordinates.
What this skill does
# Open-Meteo Flood Fetch ## Core Goal - Fetch Open-Meteo flood data for one or more coordinates in one invocation. - Support inclusive `start_date` and `end_date` windows. - Return machine-readable JSON with request metadata, transport info, validation summary, and normalized records. - Keep runtime observable with structured logs and optional log file output. ## Required Environment - Configure runtime by environment variables (see `references/env.md`). - Start from `assets/config.example.env`. - Load env values before running commands: ```bash set -a source assets/config.example.env set +a ``` ## Workflow 1. Validate effective configuration. ```bash python3 scripts/open_meteo_flood_fetch.py check-config --pretty ``` 2. Dry-run the request plan first. ```bash python3 scripts/open_meteo_flood_fetch.py fetch \ --location 52.52,13.41 \ --start-date 2026-03-01 \ --end-date 2026-03-05 \ --daily-var river_discharge \ --timezone GMT \ --dry-run \ --pretty ``` 3. Run the fetch with validation and operational logs. ```bash python3 scripts/open_meteo_flood_fetch.py fetch \ --location 52.52,13.41 \ --location 48.85,2.35 \ --start-date 2026-03-01 \ --end-date 2026-03-05 \ --daily-var river_discharge \ --daily-var river_discharge_p75 \ --ensemble \ --cell-selection nearest \ --timezone GMT \ --output ./data/open-meteo/open-meteo-flood-fetch.json \ --log-level INFO \ --log-file ./logs/open-meteo-flood-fetch.log \ --pretty ``` ## Built-in Robustness - Retry transient HTTP and network failures with exponential backoff. - Respect `Retry-After` when present and fail fast when it exceeds configured cap. - Throttle request rate with minimum request interval. - Enforce safety caps before remote calls: - maximum locations - maximum day range - maximum daily variables - Validate transport: - HTTP status handling - JSON content-type - UTF-8 strict decode - JSON parse - Validate structure: - response object/list shape - `daily` and `daily_units` presence - time axis parseability and range checks - requested variable presence and aligned array lengths - optional ensemble member field alignment when `--ensemble` is enabled ## Scope Decision - Keep one atomic fetch implementation for the Open-Meteo flood endpoint only. - Do not embed alert thresholds, geocoding, polling loops, or flood interpretation logic. - If recurring execution is needed, let OpenClaw orchestrate repeated calls externally. ## References - `references/env.md` - `references/open-meteo-flood-api-notes.md` - `references/open-meteo-flood-limitations.md` - `references/openclaw-chaining-templates.md` ## Script - `scripts/open_meteo_flood_fetch.py` ## OpenClaw Invocation Compatibility - Keep trigger metadata in `name`, `description`, and `agents/openai.yaml`. - Invoke with `$open-meteo-flood-fetch`. - Keep calls atomic and parameterized by: - `--location` - `--start-date` - `--end-date` - `--daily-var` - `--ensemble` - `--cell-selection` - Use OpenClaw orchestration, not this script, for recurring jobs. ## OpenClaw Prompt Templates Use these templates directly in OpenClaw and only replace bracketed placeholders. 1. Recon (dry-run) ```text Use $open-meteo-flood-fetch. Run: python3 scripts/open_meteo_flood_fetch.py fetch \ --location [LATITUDE,LONGITUDE] \ --start-date [YYYY-MM-DD] \ --end-date [YYYY-MM-DD] \ --daily-var river_discharge \ --timezone GMT \ --dry-run \ --pretty Return only the JSON result. ``` 2. Fetch (flood verification window) ```text Use $open-meteo-flood-fetch. Run: python3 scripts/open_meteo_flood_fetch.py fetch \ --location [LATITUDE,LONGITUDE] \ --start-date [YYYY-MM-DD] \ --end-date [YYYY-MM-DD] \ --daily-var river_discharge \ --daily-var river_discharge_p75 \ --ensemble \ --cell-selection nearest \ --timezone GMT \ --pretty Return only the JSON result. ``` 3. Validate (quality gate) ```text Use $open-meteo-flood-fetch. Run: python3 scripts/open_meteo_flood_fetch.py fetch \ --location [LATITUDE,LONGITUDE] \ --start-date [YYYY-MM-DD] \ --end-date [YYYY-MM-DD] \ --daily-var river_discharge \ --timezone GMT \ --pretty Check validation_summary.total_issue_count and validation_summary.ok. Return JSON plus one-line pass/fail verdict. ```
Related in Backend & APIs
jfrog
IncludedInteract with the JFrog Platform via the JFrog CLI and REST/GraphQL APIs. Use this skill when the user wants to manage Artifactory repositories, upload or download artifacts, manage builds, configure permissions, manage users and groups, work with access tokens, configure JFrog CLI servers, search artifacts, manage properties, set up replication, manage JFrog Projects, run security audits or scans, look up CVE details, query exposures scan results from JFrog Advanced Security, manage release bundles and lifecycle operations, aggregate or export platform data, or perform any JFrog Platform administration task. Also use when the user mentions jf, jfrog, artifactory, xray, distribution, evidence, apptrust, onemodel, graphql, workers, mission control, curation, advanced security, exposures, or any JFrog product name.
cupynumeric-migration-readiness
IncludedPre-migration readiness assessor for porting NumPy to cuPyNumeric. Use BEFORE substantial porting work begins when the user asks whether code will scale on GPU, whether they should migrate to cuPyNumeric, which NumPy patterns transfer cleanly, what must be refactored before porting, or mentions pre-port assessment, scaling analysis, or refactor planning. Inspect the user's source code, look up NumPy usage, cross-reference the cuPyNumeric API support manifest, and distinguish distributed-scaling-friendly patterns from blockers such as unsupported APIs, scalar synchronization, host round-trips, Python/object-heavy control flow, shape/data-dependent branching, and in-place mutation hazards. Produce a verdict of READY, LIGHT REFACTOR, SIGNIFICANT REFACTOR, or NOT RECOMMENDED, with concrete refactor pointers.
alibabacloud-data-agent-skill
IncludedInvoke Alibaba Cloud Apsara Data Agent for Analytics via CLI to perform natural language-driven data analysis on enterprise databases. Data Agent for Analytics is an intelligent data analysis agent developed by Alibaba Cloud Database team for enterprise users. It automatically completes requirement analysis, data understanding, analysis insights, and report generation based on natural language descriptions. This tool supports: discovering data resources (instances/databases/tables) managed in DMS, initiating query or deep analysis sessions, real-time progress tracking, and retrieving analysis conclusions and generated reports. Use this Skill when users need to query databases, analyze data trends, generate data reports, ask questions in natural language, or mention "Data Agent", "data analysis", "database query", "SQL analysis", "data insights".
token-optimizer
IncludedReduce OpenClaw token usage and API costs through smart model routing, heartbeat optimization, budget tracking, and native 2026.2.15 features (session pruning, bootstrap size limits, cache TTL alignment). Use when token costs are high, API rate limits are being hit, or hosting multiple agents at scale. The 4 executable scripts (context_optimizer, model_router, heartbeat_optimizer, token_tracker) are local-only — no network requests, no subprocess calls, no system modifications. Reference files (PROVIDERS.md, config-patches.json) document optional multi-provider strategies that require external API keys and network access if you choose to use them. See SECURITY.md for full breakdown.
resend-cli
IncludedUse this skill when the task is specifically about operating Resend from an AI agent, terminal session, or CI job via the official resend CLI: installing/authenticating the CLI, sending/listing/updating/cancelling emails, batch sends, domains and DNS, webhooks and local listeners, inbound receiving, contacts, topics, segments, broadcasts, templates, API keys, profiles, or debugging Resend CLI/API failures. Trigger on mentions of Resend CLI, `resend`, `resend doctor`, `resend emails send`, `resend domains`, `resend webhooks listen`, `resend emails receiving`, or agent-friendly terminal automation.
alibabacloud-odps-maxframe-coding
IncludedUse this skill for MaxFrame SDK development and documentation navigation on Alibaba Cloud MaxCompute (ODPS). Helps answer MaxFrame API, concept, official example, and supported pandas API questions; create data processing programs; read/write MaxCompute tables; debug jobs (remote or local); and build custom DPE runtime images. Trigger when users mention MaxFrame, MaxCompute with MaxFrame, ODPS table processing, DPE runtime, MaxFrame docs/examples, DataFrame/Tensor operations, or GPU runtime setup. Works for both English and Chinese queries about Alibaba Cloud data processing with MaxFrame.