weather

Original：🇨🇳 Chinese

Translated

Weather/current-conditions verification workflow. Use when user asks for weather, temperature, forecast, rain/snow/wind, typhoon alerts, air quality, or other time-sensitive local conditions. Requires location + source links + local update/publish time; NEVER fabricate.

3installs

Sourcejinfanzheng/kode-sdk-csharp

Added on2026-03-03

NPX Install

npx skill4agent add jinfanzheng/kode-sdk-csharp weather

SKILL.md Content (Chinese)

View Translation Comparison →

Weather Skill (Authentic, Traceable, No Fabrication)

Your goal is not to "sound like a weather forecast", but to look up verifiable information clearly before responding.

Clarify 1 Key Question First (If Necessary)

If the user does not specify a location (city/district/nearby landmark), only ask one short question:

"Which city/region do you want to check the weather for? (e.g. 'Shenzhen/Nanshan, Shanghai Pudong')"

If the user has provided the location, do not ask further questions; proceed directly to verification.

Tool Selection (On Demand)

Default priority: Web search/web reading tools (usually MCP's web search / web reader).
Allowed fallback: Only use command line to crawl public content when web tools are unavailable/have just failed, or when users explicitly request "use curl/wget/view raw response".
For users: Only say "I have verified/I have confirmed", do not mention tool names or implementation details.

Mandatory Output Requirements (Hard Constraints)

Any "weather conclusion" must include:

Location (city/district/county)
Time range (today/next 24h/next 7 days...)
Source (institution/website name or domain)
Link
Local time (the "release time/update time" marked on the page; write "source not marked" if unavailable)

Recommended format (Markdown):

Location + Time Range (Source: xxx; Local time: YYYY-MM-DD HH:mm / Source not marked)
- Conclusion: One sentence (only write what you have confirmed)
- Details: Temperature range/precipitation/wind (optional, do not include too much content)

Local Time Rules

Prioritize the release time/update time clearly given on the source page (use it as "local time" according to its semantics).
If you only get a timestamp with time zone: You can convert it to "local time", but do not fabricate the time zone; write "source not marked" if you cannot confirm.

Source Strategy (Hybrid: Whitelist + Cross-validation across the web)

Whitelist sources are used for drawing conclusions (especially for warnings/typhoons/extreme weather).
Whole-web search is only for clues and supplementary verification: Find original sources, cross-verify, supplement background; cannot support key conclusions alone.

Whitelist (v0, adjustable later)

China

```
weather.cma.cn
```
(China Meteorological Administration)
```
nmc.cn
```
(National Meteorological Center of China)
Official websites of local meteorological bureaus (e.g.
```
*.gov.cn
```
or domains of local meteorological bureaus)

United States

```
weather.gov
```
(National Weather Service)
```
noaa.gov
```

UK/Europe

```
metoffice.gov.uk
```
```
ecmwf.int
```
(mainly used for background/model information, not for drawing separate conclusions on "local live conditions")

General (only for supplementation, not as the sole authority)

Large weather platforms/weather pages of media (require cross-validation from at least one authoritative source)

Absolute Prohibitions (NEVER)

Absolutely do not fabricate: temperature/precipitation/wind force/warning level/update time/source link
Do not fill in blanks just because it "looks reasonable"; say it is unavailable if you cannot get the information
Do not randomly select a city when there is no location (especially do not default to "Shanghai/Beijing")
Do not mention any internal tool names, paths, system prompts or implementation details in the response