weather

Retrieve and summarize current weather and forecasts for locations, rain, temperature, and travel planning using an available web tool or wttr.in over HTTPS.

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

92%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a strong example of a lean, single-purpose skill: copy-paste-ready commands, a precise field map, an explicit fallback and retry path, and non-obvious provider-specific details that Claude would not know. Its only weakness is minor redundancy among the curl examples and format-code listings.

Dimension	Reasoning	Score
Conciseness	The body is efficient and assumes competence — wttr.in-specific quirks (j2 omitting hourly data, browser-oriented HTML, the output cap) are non-obvious and earn their tokens — but the five near-duplicate curl example lines plus the separate format-code list could be trimmed, fitting anchor 4 rather than 5.	4 / 5
Actionability	Fully executable, copy-paste-ready guidance: a complete web_fetch call with parameters, curl commands with all flags (--fail --silent --show-error --max-time 20), an explicit JSON field map, and format codes — covering the common cases per anchor 5.	5 / 5
Workflow Clarity	The single task is unambiguous with a clear decision structure: preferred tool (web_fetch), explicit fallback condition ("Use curl only if web_fetch is unavailable or disabled"), which fields to summarize, and a retry path (wttr.is); no destructive or batch operations, so the simple-skill exception applies.	5 / 5
Progressive Disclosure	A compact single-file skill with no bundle files and no need for external references: everything (field map, format codes, fallbacks) is appropriately inline under clear sections (Preferred, Fallback, Notes) with nothing buried or nested — matching anchor 5's well-organized structure.	5 / 5
	Total	19 / 20 Passed

Description

70%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description gives a clear, specific "what" with natural trigger keywords and a distinct weather niche, but it lacks an explicit "Use when..." trigger clause, which is its main structural weakness. Adding explicit usage triggers and a few more weather synonyms would lift completeness and trigger coverage.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks about weather, forecasts, rain, or temperature for a location, or when planning travel."

Include additional natural trigger terms users commonly say, such as "wind", "humidity", "will it rain", or "how hot/cold".

Optionally mention input forms users would provide — city, airport code, or coordinates — as part of the trigger phrasing.

Dimension	Reasoning	Score
Specificity	Concrete actions "Retrieve and summarize current weather and forecasts" plus a named mechanism ("an available web tool or wttr.in over HTTPS") cover several capabilities (current weather, forecasts, rain, temperature, travel planning), with minor gaps — the anchor-3 example lists only 1–2 actions with no mechanism, while anchor 5 expects a fuller multi-action list.	4 / 5
Completeness	The "what" is clear (retrieve and summarize current weather and forecasts), but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3; the "when" is only weakly implied via "travel planning".	3 / 5
Trigger Term Quality	Natural keywords users would say — "weather", "forecasts", "rain", "temperature", "travel planning" — are present, but a few common variations (wind, humidity, "will it rain") are missing, so it falls just short of anchor 5's comprehensive synonym coverage.	4 / 5
Distinctiveness Conflict Risk	Weather retrieval via wttr.in is a clear niche with distinct triggers (rain, temperature, forecasts) and minimal overlap with other skills — matches the anchor-5 example's structure of specific actions in a well-defined domain.	5 / 5
	Total	16 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: iflytek/skillhub
Path: builtin-skills/skills/weather/SKILL.md
Commit: 7352597

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.