Claude
Skill
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.
Virus-scanned
Reviewed automatically before listing.
Download
curie-eng-curie-examples_weather_skills_weather-5a90bfa.zip · 1 KB
Install
skills CLI
npx skills add https://github.com/curie-eng/curie/tree/main/examples/weather/skills/weather
Claude Code
claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install curie-eng-curie@llmmart
Git
git clone https://github.com/curie-eng/curie.git
The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole curie-eng/curie collection as a plugin from our marketplace. Git is the plain clone.
Skill manifest
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
<city> weather forecast <date>to 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.
Files (curie)
-
SKILL.md 2.2 KB
--- name: weather description: 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. allowed-tools: - WebSearch - WebFetch --- # 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 1. **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. 2. **Resolve the location.** If the user named it, use it. If not, ask one short question instead of guessing. 3. **Search to find a source, not to get the answer.** Run a web search like `<city> weather forecast <date>` to 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. 4. **Fetch the actual source.** `WebFetch` the 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**. 5. **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. 6. **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.
Comments (0)
Sign in to join the conversation.
Reviews (0)
No reviews yet.
No comments yet.