CtrlK
BlogDocsLog inGet started
Tessl Logo

weather

Get current weather and forecasts via wttr.in or Open-Meteo. Use when: user asks about weather, temperature, or forecasts for any location. NOT for: historical weather data, severe weather alerts, or detailed meteorological analysis. No API key needed.

68

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

88%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 a lean, fully executable command reference: every snippet runs as-is, common user questions have ready-made recipes, and the use/not-use and location guidance is crisp. The only improvements are trimming the small overlap between the Commands and Quick Responses sections and splitting the format-code/variant detail into a short reference file if the skill grows.

DimensionReasoningScore

Conciseness

The body is efficient — commented, executable curl examples with almost no explanatory padding — but has minor trimmable redundancy: the intro line repeats the title and the 'Quick Responses' section re-composes format codes already documented under 'Format Options' and 'Format Codes'.

4 / 5

Actionability

Every example is a copy-paste-ready curl command covering the common cases: current conditions, 3-day/week/specific-day forecasts, one-liners, JSON, and PNG output, plus ready recipes for 'What's the weather?', 'Will it rain?', and 'Weekend forecast'.

5 / 5

Workflow Clarity

This is a simple single-task skill and the single action is unambiguous: the flow (always include a location, pick units with &m/&u, pick the format/day option) is laid out explicitly; it is non-destructive, so no validation-checkpoint cap applies.

5 / 5

Progressive Disclosure

Sections are clearly headed and well organized with no external files (none needed at this size), but at ~110 lines all format-code and response-variant detail is inline with no reference split, which is 'good structure; minor organization gaps' rather than the well-signaled one-level-deep references of level 5.

4 / 5

Total

18

/

20

Passed

Description

82%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 strong: it clearly states what the skill does and when to use it, uses natural trigger terms, and explicitly delimits its scope with a NOT-for list. Its only weakness is modest action specificity — it names two capabilities (current weather, forecasts) without hinting at the richer functionality (units, formats, JSON/PNG output) documented in the body.

Suggestions

Add one or two more concrete capabilities to the description, e.g., "...via wttr.in or Open-Meteo, with one-line summaries, 3-day/week forecasts, and JSON or PNG output".

Include a few more natural trigger synonyms users would say, such as rain, humidity, wind, or 'will it rain', to broaden matching.

DimensionReasoningScore

Specificity

"Get current weather and forecasts via wttr.in or Open-Meteo" names the domain and exactly two concrete actions, matching the 'names domain and 1-2 concrete actions, but not comprehensive' anchor rather than the 'several specific actions' of level 4.

3 / 5

Completeness

It explicitly answers both what ("Get current weather and forecasts via wttr.in or Open-Meteo") and when ("Use when: user asks about weather, temperature, or forecasts for any location", plus an explicit NOT-for exclusion list), matching the top anchor for both what AND when with concrete triggers.

5 / 5

Trigger Term Quality

"weather, temperature, or forecasts for any location" covers the natural phrases users say, but common variations like rain, humidity, wind, or hot/cold are missing, fitting the 'good keyword coverage; a few natural terms missing' anchor.

4 / 5

Distinctiveness Conflict Risk

A clear niche (live weather lookups via named services) with explicit negative boundaries ("NOT for: historical weather data, severe weather alerts, or detailed meteorological analysis") minimizing overlap with adjacent skills.

5 / 5

Total

17

/

20

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.

Validation — 13 / 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
trpc-group/trpc-agent-go
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.