CtrlK
BlogDocsLog inGet started
Tessl Logo

weather

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

64

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/weather/SKILL.md

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

SKILL.md
Quality
Evals
Security

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 excellent lean reference: executable commands with sample outputs, a clear primary-to-fallback layout, and just the right amount of detail for a simple skill. It assumes Claude's competence and wastes no tokens.

DimensionReasoningScore

Conciseness

The body is lean and efficient: every line is an executable command, a format code, or a practical tip, with no padding or explanation of concepts Claude already knows, matching anchor 3.

3 / 3

Actionability

It provides fully executable curl one-liners with sample outputs, compact format strings, and a JSON fallback endpoint that are copy-paste ready, matching anchor 3.

3 / 3

Workflow Clarity

As a simple single-purpose skill it presents a clear primary (wttr.in) to fallback (Open-Meteo) structure with well-organized sections and no destructive or batch operations requiring validation checkpoints, so per the scoring notes it qualifies for 3.

3 / 3

Progressive Disclosure

At under 50 lines with no need for external references, the well-organized sectioned structure (wttr.in primary, Open-Meteo fallback, format codes, tips) satisfies the guideline allowing a score of 3 for simple skills.

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 clear and distinctive but stops short of a complete, trigger-rich specification: it states what the skill does without an explicit "Use when" clause or a fuller set of natural keyword variations. It is third-person and free of fluff.

Suggestions

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

Broaden natural keywords to include common variations users say, such as temperature, rain, humidity, and conditions.

Consider listing a couple more concrete actions (e.g. get hourly forecasts, fetch JSON for programmatic use) to lift specificity from anchor 2 to anchor 3.

DimensionReasoningScore

Specificity

"Get current weather and forecasts" names the weather domain and two concrete actions, but does not list a comprehensive set of specific actions, matching anchor 2.

2 / 3

Completeness

The description states what the skill does (get weather and forecasts) but provides no "Use when..." trigger guidance, which per the guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

"current weather" and "forecasts" are natural terms a user would say, but common variations like temperature, rain, or conditions are absent, so coverage is partial rather than complete.

2 / 3

Distinctiveness Conflict Risk

Weather is a clear, narrow niche with distinct triggers that is unlikely to conflict with other skills, matching anchor 3.

3 / 3

Total

9

/

12

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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
Reviewed

Table of Contents

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.