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 ./bot/workspace/skills/weather/SKILL.md
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 exemplar of a lean, executable single-purpose skill: copy-paste-ready commands, minimal prose, and clean section organization. The only minor gap is the Open-Meteo fallback giving slightly less concrete geocoding guidance.

Suggestions

For the Open-Meteo fallback, add a concrete example of resolving a city to coordinates (e.g. a geocoding curl or a noted latitude/longitude lookup) so that path is as copy-paste ready as wttr.in.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence: it jumps straight to executable one-liners, format codes, and tips with no explanation of what weather or curl is, matching the level-3 anchor where every token earns its place.

3 / 3

Actionability

Commands are fully executable and copy-paste ready with sample outputs (e.g. `curl -s "wttr.in/London?format=3"` → "London: ⛅️ +8°C") plus concrete format codes and flags, matching the level-3 anchor.

3 / 3

Workflow Clarity

This is a simple single-purpose skill whose single action (curl a weather URL) is unambiguous; per the simple-skills scoring note, workflow clarity can score 3 here, and no destructive or batch validation is needed.

3 / 3

Progressive Disclosure

Under 50 lines with no external references and no bundle files, the content is well-organized into clear primary (wttr.in) and fallback (Open-Meteo) sections, satisfying the level-3 simple-skills criterion.

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 concise and covers a clearly distinct niche, but it lacks explicit "Use when..." trigger guidance and only broadly names its actions. Adding a trigger clause and a few more natural keywords would lift the weaker dimensions.

Suggestions

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

Include more natural user terms like "temperature", "rain", "humidity", or "forecast for [city]" to broaden trigger coverage.

Optionally enumerate a couple more concrete capabilities (e.g. "get hourly/daily forecasts, check conditions") to push specificity toward 3.

DimensionReasoningScore

Specificity

"Get current weather and forecasts" names two concrete actions and a constraint ("no API key required"), but it is not a comprehensive enumeration of multiple distinct capabilities, so it stops short of the level-3 anchor.

2 / 3

Completeness

It states what the skill does ("Get current weather and forecasts") but has no "Use when..." clause or equivalent trigger guidance, which caps completeness at 2 per the judging guidelines.

2 / 3

Trigger Term Quality

Natural terms like "weather" and "forecasts" are present and would be said by users, but common variations such as "temperature", "rain", or "forecast for [city]" are missing, matching the level-2 anchor.

2 / 3

Distinctiveness Conflict Risk

Weather lookup is a clear, narrow niche with triggers unlikely to overlap with other skills, matching the level-3 anchor for a distinct niche.

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
volcengine/OpenViking
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.