Weather
Look up a location's weather forecast using a live web search. Invoke whenever the user asks about the weather, whether to expect rain, temperature, or what to wear or plan for outdoor activities.
Install
$ agentstack add skill-curie-eng-curie-weather ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-curie-eng-curie-weather) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Weather
When to run
The user asks about the weather, a forecast, temperature, rain or snow chances, or whether a day suits an outdoor plan.
How to answer
- Fix the date first. Note today's date from the environment. Resolve "today", "tomorrow", or a weekday into an explicit calendar date (e.g. "Wed, July 8, 2026"). Carry that date through every step.
- Resolve the location. If the user named it, use it. If not, ask one short question instead of guessing.
- Search to find a source, not to get the answer. Run a web search like
weather forecastto locate a forecast page. Do NOT report numbers from the search-result summary itself. Those summaries frequently merge the wrong day or location and are the top cause of a wrong forecast. - Fetch the actual source.
WebFetchthe forecast page (prefer a national weather service such as weather.gov, or a major provider). Read the high, low, sky, and precipitation for the exact date you fixed in step 1. - Verify the date matches before you report. The fetched forecast must state the day you were asked about. If the page shows a different date, or you cannot fetch a page whose date matches, do not report a number. Say what you tried and that you could not confirm a current forecast. A plausible-looking summary for the wrong day is worse than saying you could not confirm.
- Report in two or three sentences: expected high and low, sky conditions, and precipitation chance, with the location and the explicit date. Then name the source you actually fetched.
Hard rules
- Report only numbers you read from a page you fetched for the matching date. Never report figures that came only from a search-result summary, and never cite a source you did not open.
- If nothing usable can be fetched and date-matched, say so and name what you tried. Do not fill the gap with a guess.
- Temperatures in Fahrenheit first, Celsius in parentheses.
- Keep the reply short enough to read in Slack without expanding.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: curie-eng
- Source: curie-eng/curie
- License: Apache-2.0
- Homepage: https://www.curietech.ai
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.