weather

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

1.19x

Quality

—

Does it follow best practices?

Impact

100%

1.19x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

100%

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 a lean, actionable single-purpose skill: executable commands with output, organized sections, and no padding, scoring at the top of every dimension.

Dimension	Reasoning	Score
Conciseness	The body is lean and efficient, presenting only curl commands, format codes, and brief tips without explaining concepts Claude already knows.	3 / 3
Actionability	Every example is a fully executable, copy-paste-ready curl command with sample output, plus a documented list of format codes and flags.	3 / 3
Workflow Clarity	This is a simple single-task skill where the action is unambiguous; the primary/fallback service structure is clearly labeled.	3 / 3
Progressive Disclosure	Under 50 lines with no need for external bundle references, the content is well-organized into clearly signaled wttr.in and Open-Meteo sections.	3 / 3
	Total	12 / 12 Passed

Description

57%

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 names concrete actions in a distinct niche, but it lacks an explicit "Use when..." trigger clause and has limited keyword coverage, leaving both completeness and trigger quality at the mid level.

Suggestions

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

Broaden natural trigger terms to include variations users say such as "temperature", "conditions", "rain", or "weather for [city]".

Consider listing a third concrete action (e.g. retrieve JSON data for programmatic use) to strengthen specificity toward score 3.

Dimension	Reasoning	Score
Specificity	"Get current weather and forecasts" names the weather domain and two concrete actions (current weather, forecasts), but is not comprehensive enough to reach the multi-action listing of score 3.	2 / 3
Completeness	It states what the skill does but provides no explicit "Use when..." trigger clause, which per the guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	"current weather" and "forecasts" are natural terms users would say, but coverage is limited and misses common variations like temperature, conditions, or rain.	2 / 3
Distinctiveness Conflict Risk	Weather is a clear, distinct niche with specific triggers unlikely to overlap with other skills.	3 / 3
	Total	9 / 12 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: HKUDS/nanobot
Commit: c9c69e4

Reviewed: 1 day 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.