Weather Brief

The Weather Brief skill generates a compact, actionable weather forecast suitable for voice playback or quick text consumption inside an OpenClaw session.

How It Works

When invoked, the agent receives the system prompt from assets/prompt.txt and a request payload containing a target city, preferred unit system, and an optional audience tag. The agent then fetches live weather data (via wttr.in or Open-Meteo, depending on available skills) and returns a short paragraph that covers:

1. Current conditions — sky state, temperature, humidity, wind.
2. Day outlook — expected highs/lows and precipitation probability.
3. Practical tip — a single recommendation tailored to the audience (e.g., "Carry an umbrella" for commuters, "UV index is high—apply sunscreen" for outdoor workers).

The output is intentionally brief (2–4 sentences) so it works well as a TTS segment in morning routines or dashboard widgets.

Inputs

Example Request

{
  "city": "Portland",
  "units": "metric",
  "audience": "commuter"
}

Example Response

Portland is 12 °C with overcast skies and light rain expected by mid-morning. Highs near 15 °C. Grab a rain jacket before you head to the train.

Lifecycle Hooks

hooks/prepare.sh

Copies assets/prompt.txt into a build/ directory alongside a generated package-info.json manifest. This makes the skill self-contained for distribution without requiring the full repo tree.

Run manually:

bash hooks/prepare.sh

hooks/validate.sh

Performs a quick structural check against SKILL.md frontmatter:

• Confirms name, version, and hooks keys exist.
• Verifies assets/prompt.txt is referenced.

Returns exit code 0 on success.

bash hooks/validate.sh

Assets

• assets/prompt.txt — System prompt injected into the agent context. It instructs the model to produce a concise, friendly weather summary with one practical recommendation.
• assets/icons/weather-brief.txt — Plain-text icon placeholder used by dashboard renderers that support ASCII badges.

Configuration Notes

• The skill does not bundle its own weather data source. It expects the host OpenClaw instance to have network access to a weather API (wttr.in is the zero-config default).
• Unit conversion is handled by the data source; the units field is passed through as a query parameter.
• For scheduled use (e.g., cron-triggered morning brief), pair with a systemEvent payload that includes the city and audience in the prompt text.

Limitations

• City name resolution depends on the upstream API's geocoder. Ambiguous names (e.g., "Springfield") may return unexpected locations. Use "Springfield, IL" for precision.
• The skill produces English-language output only in the current version.
• Severe weather alerts are not included; this is a casual briefing, not a safety tool.