Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Fetch surf-relevant ocean conditions from Stormglass by spot name or coordinates, including current snapshot and 1-3 day forecast windows with tides, gusts,...
Fetch surf-relevant ocean conditions from Stormglass by spot name or coordinates, including current snapshot and 1-3 day forecast windows with tides, gusts,...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Produce machine-readable surf condition data for cron-driven agent pipelines. This skill resolves a surf spot name with Google Geocoding (or uses direct coordinates), queries Stormglass, and returns a stable JSON payload for downstream interpretation/rendering.
Provide exactly one location mode: --location "Spot name" (optional country/region in string), or --lat <float> --lon <float> Optional controls: --horizon now|24h|48h|72h (default 72h) --output json|pretty (default json, recommended for automation) --source <comma-separated provider list> --mock (offline deterministic data; useful for tests)
STORMGLASS_API_KEY for Stormglass requests GOOGLE_GEOCODING_API_KEY optional for --location (if absent, script falls back to OpenStreetMap Nominatim) In --mock mode, no API keys are required.
ModeSTORMGLASS_API_KEYGOOGLE_GEOCODING_API_KEY--mocknot requirednot requiredlive --lat/--lonrequirednot requiredlive --location with Googlerequiredoptional (preferred when set)live --location with OSM fallbackrequirednot required Primary credential is STORMGLASS_API_KEY.
JSON output for cron: python scripts/surf_report.py --location "Highcliffe Beach" --horizon 72h --output json Direct coordinates: python scripts/surf_report.py --lat 50.735 --lon -1.705 --horizon 24h --output json Offline test run: python scripts/surf_report.py --location "Highcliffe Beach" --horizon now --mock --output json
Top-level keys are stable: meta: request metadata, timestamps, input mode, optional warnings location: resolved place details and coordinates now: instantaneous surf-relevant metrics forecast: horizon summaries and best windows tides: tide extremes and inferred current tide trend Expected metric coverage (null if unavailable): waveHeightM swellHeightM swellPeriodS swellDirectionDeg windSpeedMps windDirectionDeg windGustMps waterTemperatureC
0: success 2: invalid CLI usage/arguments 3: missing API keys/configuration 4: external API failure (geocoding/Stormglass) 5: response parsing/normalization failure
Prefer --output json for downstream agents. Treat null metrics as "not provided by source", not zero. Read field-level details in reference.md. Use examples.md for prompt and command patterns. Use scripts/test_surf_report.py before cron rollout. Optional: use scripts/normalize_surf_data.py to enforce strict schema defaults before rendering.
Data access, storage, extraction, analysis, reporting, and insight generation.
Largest current source with strong distribution and engagement signals.