MicrosoftKnown publishermicrosoft/AgentHosting.Cli/src/Microsoft.Agents.Hosting.Cli.E2E/fixtures/MCSCliAgent/behaviors/get-us-weather/SKILL.mdget-us-weather
Skill3 starsChanged 6 days agoMITView on GitHub
Get the current weather (temperature, sky conditions, wind, humidity) for any city or town in the United States. Use when the user asks about the current weather, temperature, or conditions in a US city, e.g. "what''s the weather in Seattle" or "how hot is it in Austin right now".
1 other project uses a version of this.
Adopted by
Most recently taken up by
- microsoft/vscode-copilotstudioword for word, first seen Nov 1, 2026
Other versions1 project uses a version of this.
Word for word · 1
- microsoft/vscode-copilotstudio★ 117100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository13 other files it gives its agents.
- .github/copilot-instructions.mdCopilot instructions
- add-channelSkill
- add-knowledgeSkill
- add-skillSkill
- clone-agentSkill
- create-agentSkill
- delete-agentSkill
- deploy-agentSkill
- publish-agentSkill
- pull-agentSkill
- get-us-temperatureSkill
- my-skill-1Skill
- skill-1Skill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
When this skill is activated:
- Distinctive: line 16
Run the helper script Get-UsWeather.ps1, passing the city (and the state when the user provided one), to look up the coordinates and fetch …
- Distinctive: line 21
Only supports locations within the United States — the National Weather Service API does not cover places outside the US.
- Distinctive: line 22
Always show the temperature in Fahrenheit for US users.
- Distinctive: line 23
Never fabricate weather values.
- Very specific: line 46
Run the script with, for example: pwsh -File ./scripts/Get-UsWeather.ps1 -City "Austin" -State "Texas".
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Get Current US City Weather
Fetches the latest observed weather for a United States city using the free Open-Meteo geocoding API and the National Weather Service (api.weather.gov), neither of which requires an API key.
When this skill is activated:
- Determine the target US city from the user's request. If the name is ambiguous (e.g. "Springfield", "Portland", "Columbus"), ask the user for the state before continuing.
- Run the helper script Get-UsWeather.ps1, passing the city (and the state when the user provided one), to look up the coordinates and fetch the latest station observation.
- Report the current temperature in °F, the sky conditions, humidity, and wind to the user in a short, friendly summary.
Guidelines
- Only supports locations within the United States — the National Weather Service API does not cover places outside the US.
- Always show the temperature in Fahrenheit for US users; you may add Celsius in parentheses.
- Never fabricate weather values. If the script returns an error or no observation, say so plainly and suggest trying a nearby larger city.
- Pass the state whenever the user gives one (or when the city name is shared by multiple states) so the correct location is selected.
- The script already sets the descriptive
User-Agentheader that api.weather.gov requires — do not remove it.
Examples
Example 1: Simple city lookup
- User request: "What's the weather in Seattle?"
- Expected behavior: Run the script for "Seattle", then reply e.g. "It's currently 62°F and partly cloudy in Seattle, WA, with 71% humidity and a light 5 mph wind."
Example 2: Ambiguous city name
- User request: "How's the weather in Portland right now?"
- Expected behavior: Ask "Portland, Oregon or Portland, Maine?", then run the script with the confirmed state before answering.
Example 3: Non-US city
- User request: "What's the weather in Paris?"
- Expected behavior: Explain that this skill only covers US cities and that Paris, France is not supported.
Notes
- "Current" conditions come from the latest station observation, which can lag real time by up to roughly one hour.
- Some stations occasionally report null values; the script automatically checks the next few nearby stations to find valid data.
- Temperature is converted from the API's Celsius values; wind speed is converted from km/h to mph.
- Run the script with, for example:
pwsh -File ./scripts/Get-UsWeather.ps1 -City "Austin" -State "Texas".
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.