weather

Get current weather and forecasts (no API key required).

Quality

79%

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

Fix and improve this skill with Tessl

tessl review fix ./SKILLs/weather/SKILL.md

Quality

Content

93%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 an exemplar of lean, executable skill content: every command runs as written, expected outputs are shown, and both a human-readable and a programmatic service are covered without a wasted token. The only weakness is the fallback workflow's unspecified coordinate-lookup step.

Suggestions

Make the Open-Meteo fallback fully executable by naming a concrete geocoding method (e.g. a sample curl to a free geocoding API or the wttr.in location itself) instead of the vague "Find coordinates for a city, then query."

Show one line of the Open-Meteo JSON response or name the key fields to parse (beyond the existing mention of temp, windspeed, weathercode) so programmatic use needs no further lookup.

Dimension	Reasoning	Score
Conciseness	The ~42-line body contains only commands, expected outputs, API facts, and one-line tips — no explanation of concepts Claude already knows and no padding. Every token earns its place, matching anchor 5 exactly.	5 / 5
Actionability	Every example is a copy-paste-ready curl command with expected output ("curl -s \"wttr.in/London?format=3\"" → "London: ⛅️ +8°C"), covering the common cases: quick one-liner, compact format, full forecast, PNG output, and a JSON fallback endpoint. This matches anchor 5's fully executable, common-case coverage.	5 / 5
Workflow Clarity	The primary (wttr.in) → fallback (Open-Meteo) structure is clear and the main action is unambiguous, but the fallback step "Find coordinates for a city, then query" gives no concrete method for obtaining coordinates — a minor gap. It sits between anchors 4 and 5; no validation checkpoints are needed since no destructive or batch operations exist.	4 / 5
Progressive Disclosure	This is a simple skill under 50 lines with no external reference material needed; the two clearly headed sections (## wttr.in, ## Open-Meteo) plus compact format-code and tips lines are well organized. Per the guidelines, simple skills with well-organized sections and no need for external references score 5.	5 / 5
	Total	19 / 20 Passed

Description

65%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 is concise and appropriately specific about what the skill does, with strong natural trigger terms and a distinct niche. Its main weakness is the missing "Use when..." clause, which caps completeness and limits trigger guidance for when Claude should invoke it.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks about the weather, a forecast, or current conditions for a location."

Broaden natural trigger vocabulary with common synonyms such as temperature, humidity, wind, or rain to strengthen trigger_term_quality and specificity.

Optionally name the distinguishing capability (e.g. curl-based lookup requiring no API key) in the description to sharpen distinctiveness for programmatic use cases.

Dimension	Reasoning	Score
Specificity	"Get current weather and forecasts" names the domain and two concrete actions, but coverage stops there — no mention of temperature, humidity, wind, or conditions. This matches anchor 3 (1-2 concrete actions, not comprehensive), not anchor 4 (several specific actions with minor gaps).	3 / 5
Completeness	The description has a clear "what" (get current weather and forecasts, no API key) but no "Use when..." clause or equivalent trigger guidance, which the guidelines explicitly cap at 3. It does not reach anchor 4, which requires both what and when.	3 / 5
Trigger Term Quality	"weather" and "forecasts" are exactly the natural phrases a user would say when needing this skill, though common variations like temperature, rain, or conditions are absent. Good keyword coverage with a few natural terms missing — noticeably above the anchor-3 midpoint but short of anchor 5's synonym/extension comprehensiveness.	4 / 5
Distinctiveness Conflict Risk	Weather lookup is a clear niche with distinct natural triggers ("weather", "forecast") and no plausible confusion with other skills. This matches anchor 5: clear niche, distinct triggers, minimal conflict risk.	5 / 5
	Total	15 / 20 Passed

Validation

81%

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 — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	13 / 16 Passed

Repository: netease-youdao/LobsterAI
Path: SKILLs/weather/SKILL.md
Commit: 791a352

Reviewed: 2 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.