agentleFS
MicrosoftKnown publishermicrosoft/AgentHosting.Cli/src/Microsoft.Agents.Hosting.Cli.E2E/fixtures/MCSCliAgent/behaviors/get-us-temperature/SKILL.md

get-us-temperature

Skill3 starsChanged 6 days agoMITView on GitHub

MD2-162228 - Get the current observed temperature for any city or town in the United States. Use when the user asks for the current temperature, how hot or cold it is, or the temperature in a US city, e.g. "what is the temperature in Seattle" or "how cold is it in Austin right now".

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 6 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    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
  1. Distinctive:

    When this skill is activated:

    line 13
  2. Distinctive:

    Run the helper script Get-UsTemperature.ps1, passing the city and the state when the user provided one, to look up the coordinates and …

    line 16
  3. Distinctive:

    Only supports locations within the United States because the National Weather Service API does not cover places outside the US.

    line 21
  4. Distinctive:

    Always show the temperature in Fahrenheit for US users.

    line 22
  5. Distinctive:

    Never fabricate temperature values.

    line 23
  6. Distinctive:

    If the user asks for broader weather details, answer with the temperature and explain that this skill is focused on temperature only.

    line 25
  7. Very specific:

    Run the script with, for example: pwsh -File ./scripts/Get-UsTemperature.ps1 -City "Austin" -State "Texas".

    line 47

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Get Current US City Temperature

Fetches the latest observed temperature for a United States city using the free Open-Meteo geocoding API and the National Weather Service (api.weather.gov), local 2 neither of which requires an API key.

When this skill is activated:

  1. 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.
  2. Run the helper script Get-UsTemperature.ps1, passing the city and the state when the user provided one, to look up the coordinates and fetch the latest station observation.
  3. Report the current temperature in Fahrenheit in a short, direct answer. Include Celsius in parentheses when useful.

Guidelines

  • Only supports locations within the United States because 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 temperature 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.
  • If the user asks for broader weather details, answer with the temperature and explain that this skill is focused on temperature only.
  • See instruction.txt for the operational instructions packaged with this skill.

Examples

Example 1: Simple city lookup

  • User request: "What is the temperature in Seattle?"
  • Expected behavior: Run the script for "Seattle", then reply e.g. "It is currently 62 F in Seattle, WA."

Example 2: Ambiguous city name

  • User request: "How cold is it 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 is the temperature in Paris?"
  • Expected behavior: Explain that this skill only covers US cities and that Paris, France is not supported.

Notes

  • "Current" temperature comes 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 temperature data.
  • Temperature is converted from the API's Celsius values.
  • Run the script with, for example: pwsh -File ./scripts/Get-UsTemperature.ps1 -City "Austin" -State "Texas".

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.