weather

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

Quality

82%

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

The canonical home for this skill is weather in deepgram/dglabs-deepclaw

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 an exemplar of a lean, executable simple skill: copy-paste curl commands with outputs, a clear primary/fallback structure, and well-organized sections with no unnecessary explanation.

Dimension	Reasoning	Score
Conciseness	The body is lean with no padding — it skips explaining what weather or curl is and gives only the service names, executable commands, format codes, and tips, so every token earns its place.	5 / 5
Actionability	Multiple copy-paste-ready curl commands are shown with example outputs and format codes, covering the common cases (one-liner, compact, full forecast, JSON fallback).	5 / 5
Workflow Clarity	This is a simple single-purpose skill with an unambiguous action and a clear primary (wttr.in) / fallback (Open-Meteo) relationship; no destructive or batch operations require validation checkpoints.	5 / 5
Progressive Disclosure	At under 50 lines with no need for external references, the well-organized sections (primary service, fallback, format codes, tips) satisfy the simple-skill exception for a top score.	5 / 5
	Total	20 / 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 clearly communicates a distinct, well-scoped capability with strong natural trigger terms. Its main weakness is the absence of an explicit "Use when..." trigger clause, which caps completeness at 3.

Suggestions

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

Include a few more concrete actions or synonyms (e.g. temperature, humidity, conditions) to broaden trigger coverage and specificity.

Dimension	Reasoning	Score
Specificity	"Get current weather and forecasts" names the weather domain with two concrete actions (current conditions, forecasts), matching the anchor for 1-2 concrete actions without being comprehensive.	3 / 5
Completeness	The description gives a clear "what" (get weather and forecasts) but lacks any "Use when..." or equivalent explicit trigger guidance, capping completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	"weather", "current weather", and "forecasts" are exactly the natural phrases a user would say, giving good keyword coverage, though a few related synonyms (e.g. temperature) are absent.	4 / 5
Distinctiveness Conflict Risk	Weather lookup is a clear, narrow niche with distinct triggers and the "no API key required" differentiator, giving minimal overlap risk with other skills.	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: Bitterbot-AI/bitterbot-desktop
Path: skills/weather/SKILL.md
Commit: 017761f

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.