stormglass_skill

This skill fetches surf conditions from Stormglass by spot name or coordinates, delivering a JSON-ready forecast and tides for downstream use.
  • Python

2.6k

GitHub Stars

5

Bundled Files

2 months ago

Catalog Refreshed

3 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill stormglass

  • _meta.json293 B
  • examples.md2.4 KB
  • README.md3.6 KB
  • reference.md3.7 KB
  • SKILL.md3.3 KB

Overview

This skill fetches surf-relevant ocean conditions from Stormglass by resolving a spot name or using direct coordinates, and returns a stable machine-readable surf report. It provides a current snapshot plus 1–3 day forecast windows with tides, gusts, and water temperature suitable for automation and cron-driven pipelines.

How this skill works

The skill accepts either a spot name (resolved with Google Geocoding or OpenStreetMap fallback) or latitude/longitude, queries Stormglass for requested horizon (now, 24h, 48h, 72h), and normalizes the provider responses into a predictable JSON contract. It includes optional mock mode for offline deterministic output and emits clear exit codes for automation.

When to use it

  • Generate automated surf reports for cron jobs or agent pipelines
  • Provide current wave, swell, wind, gust, tide, and water temperature data for a beach or surf spot
  • Power a downstream renderer or chatbot that needs stable JSON surf data
  • Run tests or CI with deterministic offline data using mock mode
  • Resolve a user-provided spot name to coordinates and fetch ocean conditions

Best practices

  • Prefer --output json for downstream agents and automation
  • Supply --lat and --lon when exact coordinates are known to avoid geocoding ambiguity
  • Set STORMGLASS_API_KEY for live requests; supply GOOGLE_GEOCODING_API_KEY to improve name resolution
  • Use --mock for deterministic tests and CI without API keys
  • Validate output with provided test script before production cron rollout

Example use cases

  • Cron job producing hourly JSON surf snapshots for a surf forecasting dashboard
  • Chatbot answers: "What are the surf conditions at Bondi Beach for the next 24 hours?"
  • Automated workflow that selects best surf windows based on swell period and tide trend
  • QA and integration tests using --mock to verify downstream parsing and rendering
  • On-demand report via coordinates for rescue or beach operations teams

FAQ

STORMGLASS_API_KEY is required for live Stormglass data. GOOGLE_GEOCODING_API_KEY is optional but recommended when using a spot name for more accurate geocoding.

What does mock mode do and when should I use it?

Mock mode returns deterministic offline data and requires no API keys; use it for local development, CI, and automated tests to avoid rate limits and external failures.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational