weather

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

Quality

70%

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

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 content is a tight, fully executable reference for two free weather services with concrete curl examples and no padding. It fully respects the simple-skill exceptions for workflow clarity and progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is lean and efficient: short commands with inline expected output and no padding explaining what curl or weather APIs are; every line earns its place.	5 / 5
Actionability	All examples are copy-paste-ready curl commands with concrete URLs, format codes, and shown outputs, covering the common cases (one-liner, compact, full forecast, JSON fallback).	5 / 5
Workflow Clarity	This is a simple single-purpose skill (under 50 lines, one task) where the action is unambiguous; the simple-skill exception applies and the single action is clear.	5 / 5
Progressive Disclosure	A short, well-organized skill under 50 lines with no need for external references; sections (primary service, fallback, tips) are clearly labeled and easy to navigate.	5 / 5
	Total	20 / 20 Passed

Description

41%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 clearly states what the skill does (weather and forecasts, no API key) but omits any explicit trigger guidance for when to invoke it. It is concise and distinct but lacks the 'when' half of a complete description.

Suggestions

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

Include a couple of natural trigger synonyms like 'temperature' or 'conditions' to improve keyword coverage.

Optionally note the free/no-key value proposition is already strong; pair it with the trigger clause to lift completeness.

Dimension	Reasoning	Score
Specificity	The phrase 'Get current weather and forecasts' names the domain and one to two concrete actions (current weather, forecasts), but offers no comprehensive coverage of capabilities like location lookup, units, or JSON output.	3 / 5
Completeness	A clear 'what' is present (get current weather and forecasts) but there is no 'Use when...' clause and 'when' is only weakly implied, which the guidelines cap at 3 at most; with no trigger guidance at all it sits below the midpoint.	2 / 5
Trigger Term Quality	'weather' and 'forecasts' are natural terms users say, but common variations like 'temperature', 'forecast for <city>', or 'conditions' are absent, leaving keyword coverage partial.	3 / 5
Distinctiveness Conflict Risk	The weather domain is a fairly distinct niche with minimal overlap with other skills, though the broad phrasing leaves minor overlap risk with general utility skills.	4 / 5
	Total	12 / 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: 100d3f7

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.