weather

Get current weather and forecasts via wttr.in or Open-Meteo. Use when: user asks about weather, temperature, or forecasts for any location. NOT for: historical weather data, severe weather alerts, or detailed meteorological analysis. No API key needed.

1.39x

Quality

92%

Does it follow best practices?

Impact

88%

1.39x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

85%

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

This is a solid, actionable skill with clear executable commands and good organization. Its main weakness is mild verbosity in the 'When to Use' / 'When NOT to Use' sections, which enumerate obvious trigger phrases that Claude can infer. The core technical content (curl commands, format codes) is lean and well-structured.

Suggestions

Condense the 'When to Use' and 'When NOT to Use' sections into a brief 2-3 line summary rather than listing individual trigger phrases Claude can already recognize.

Dimension	Reasoning	Score
Conciseness	The 'When to Use' and 'When NOT to Use' sections are somewhat verbose for Claude's capabilities—Claude doesn't need trigger phrase examples listed out. The format codes reference and command examples are efficient, but the overall document could be tightened by removing the obvious use-case enumeration.	2 / 3
Actionability	All commands are fully executable curl commands that are copy-paste ready. Format codes are clearly documented, and multiple concrete examples cover different use cases (current weather, forecasts, specific formats, JSON output).	3 / 3
Workflow Clarity	This is a simple, single-purpose skill (run a curl command, return results). There are no multi-step destructive operations requiring validation checkpoints. The commands are clearly categorized and unambiguous.	3 / 3
Progressive Disclosure	For a simple skill with no bundle files and under ~80 lines of meaningful content, the organization into clear sections (Commands, Format Options, Format Codes, Quick Responses, Notes) is well-structured and easy to navigate without needing external references.	3 / 3
	Total	11 / 12 Passed

Description

100%

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

This is an excellent skill description that clearly communicates what it does, when to use it, and importantly what it should NOT be used for. The inclusion of specific API services (wttr.in, Open-Meteo), natural trigger terms, explicit scope boundaries, and the note about no API key needed makes this highly actionable for skill selection. It follows all best practices including third-person voice and concise formatting.

Dimension	Reasoning	Score
Specificity	Lists specific concrete actions: 'Get current weather and forecasts', names specific services 'wttr.in or Open-Meteo', and explicitly states what it does NOT do (historical data, severe weather alerts, detailed meteorological analysis).	3 / 3
Completeness	Clearly answers both 'what' (get current weather and forecasts via wttr.in or Open-Meteo) and 'when' (explicit 'Use when: user asks about weather, temperature, or forecasts for any location'). Also includes a 'NOT for' clause which further clarifies scope.	3 / 3
Trigger Term Quality	Includes natural keywords users would say: 'weather', 'temperature', 'forecasts', 'location'. These are exactly the terms a user would use when asking about weather conditions.	3 / 3
Distinctiveness Conflict Risk	Very clear niche focused on weather queries via specific APIs. The explicit 'NOT for' exclusions (historical data, severe alerts, meteorological analysis) further reduce conflict risk with any more specialized weather or data analysis skills.	3 / 3
	Total	12 / 12 Passed

Validation

72%

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 — 8 / 11 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	8 / 11 Passed

Repository: Hung-Reo/hungreo-openclaw
Commit: d8d7f4b

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