Weather Query

Problem It Addresses

Manual weather lookup often involves opening a browser or app, entering a city, waiting for the page to refresh, and copying fields such as temperature, humidity, and wind. In an Agent workflow, this is better handled as a text query: given a city or region, retrieve current weather, forecasts, and date-based query results where supported.

How It Works

The skill centers on the Weather capability, described as Get current weather and forecasts (no API key required). Inputs include instruction and optional context: instruction carries the user request, such as city name, query type, date, or fields of interest, while context supplies surrounding information.
Key steps usually include:
- Confirming the Agent environment supports SKILL.md, for example Claude Code, Cursor, Codex, or Gemini CLI;
- Querying current weather, forecasts for the next 1-7 days, or a specific date when supported;
- Inspecting returned fields such as temperature, humidity, wind speed, and pressure;
- Debugging empty results, parameter errors, or network issues by checking input format, connectivity, and data source status.

Boundaries And Notes

The materials classify it as a lifestyle-service weather skill and say it currently supports Chinese queries. It is not suitable for complex decisions that require human judgment. For travel, fieldwork, logistics, or outdoor plans, treat the weather output as supporting information rather than the sole basis for action. The materials also mention both no API key requirement and API key configuration notes, so actual deployment should follow the runtime prompt and credential availability.