weather

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

Quality

76%

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 ./bot/workspace/skills/weather/SKILL.md

Quality

Content

100%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 exemplary lean, fully-actionable weather lookup skill — copy-paste commands for both services, a compact format-code reference, and well-organized sections with no unnecessary explanation.

Dimension	Reasoning	Score
Conciseness	The body is lean — a one-line framing ("Two free services, no API keys needed.") followed by copy-paste curl commands, a compact format-code reference, and terse tips, with no padding explaining what curl or weather APIs are.	5 / 5
Actionability	All examples are fully executable curl one-liners covering the common cases (one-liner, compact, full forecast, PNG, JSON fallback), with concrete format codes and URL-encoding notes.	5 / 5
Workflow Clarity	This is a single-purpose query skill with unambiguous primary (wttr.in) and fallback (Open-Meteo JSON) paths clearly labeled; the simple-skill exception applies and no destructive/batch operation requires validation checkpoints.	5 / 5
Progressive Disclosure	Well under 50 lines with no need for external references, organized into clear sections (wttr.in, format codes, tips, Open-Meteo); the simple-skill exception rewards this with a top score.	5 / 5
	Total	20 / 20 Passed

Description

53%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 third-person with a clear, distinctive niche, but it omits an explicit 'Use when...' trigger clause and natural trigger-term variations, which cap completeness and trigger quality at the midpoint.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks for current weather, forecasts, or temperature for a city or airport."

Broaden natural trigger terms to include "weather report", "temperature", "humidity", and "wind" so common phrasings match.

Optionally note the programmatic fallback (JSON via Open-Meteo) in the description to widen coverage.

Dimension	Reasoning	Score
Specificity	"Get current weather and forecasts" names the weather domain and two concrete actions (current weather, forecasts), but the coverage is not comprehensive — no mention of units, location formats, or programmatic output.	3 / 5
Completeness	The what ("Get current weather and forecasts") is clear, but there is no "Use when..." clause or equivalent explicit trigger guidance, which per the rubric caps completeness at 3.	3 / 5
Trigger Term Quality	"current weather and forecasts" supplies relevant keywords but misses common variations users say (e.g. "weather report", "temperature", "rain chance", "humidity").	3 / 5
Distinctiveness Conflict Risk	"Get current weather and forecasts (no API key required)" carves a clear, low-conflict niche; just below 5 because it lacks explicit trigger phrases that would make it unmistakable.	4 / 5
	Total	13 / 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: volcengine/OpenViking
Path: bot/workspace/skills/weather/SKILL.md
Commit: dbf3fcc

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