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.

70

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A lean, highly actionable single-purpose skill with executable curl commands and clear organization. The main weakness is redundancy across the Format Options, Format Codes, and Quick Responses sections, which inflates token usage without adding capability.

Suggestions

Consolidate the overlapping Format Options, Format Codes, and Quick Responses sections so each curl variant appears once; this removes redundancy and improves conciseness.

Drop the 'Notes' restatement of 'No API key needed' since it already appears in the description frontmatter, or trim Notes to only novel caveats (rate limiting, airport codes).

DimensionReasoningScore

Conciseness

The body is mostly command-focused and avoids explaining concepts Claude knows, but the Format Options, Format Codes, and Quick Responses sections repeat overlapping curl variants, and the Notes section restates 'No API key needed' from the description, so it could be tightened — matching the level-2 rather than level-3 anchor.

2 / 3

Actionability

It provides fully executable, copy-paste-ready curl commands with concrete format codes and worked examples for each intent, matching the level-3 anchor for specific executable guidance.

3 / 3

Workflow Clarity

This is a simple single-task skill where the action (run a curl command) is unambiguous and involves no destructive or batch operations needing validation, so per the simple-skills scoring note workflow clarity scores 3.

3 / 3

Progressive Disclosure

No bundle files are provided and none are needed for this simple skill; content is organized into clearly labeled, navigable sections with no nested references, matching the well-organized-structure basis for a level-3 score.

3 / 3

Total

11

/

12

Passed

Description

90%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that clearly states capabilities, triggers, and exclusions in third person with natural keywords. The only weakness is that the action list is narrow (current weather and forecasts) rather than a comprehensive set of concrete operations.

Suggestions

Expand the capability list beyond 'current weather and forecasts' to name a few more concrete actions (e.g., hourly forecasts, per-day breakdowns, JSON/PNG output) to lift specificity toward the level-3 anchor.

The phrase 'or Open-Meteo' is mentioned in the description but never referenced in the body; either add Open-Meteo usage guidance or drop the mention to avoid an unfulfilled capability claim.

DimensionReasoningScore

Specificity

It names the domain and two actions ("Get current weather and forecasts via wttr.in or Open-Meteo"), but does not enumerate a comprehensive set of distinct concrete actions, matching the level-2 anchor rather than the multi-action level-3 example.

2 / 3

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"), with explicit triggers plus a NOT-for clause, matching the level-3 anchor.

3 / 3

Trigger Term Quality

Natural user phrasings are well covered ("weather, temperature, or forecasts for any location"), which are exactly the terms a user would say, matching the level-3 anchor for good coverage of natural terms.

3 / 3

Distinctiveness Conflict Risk

A clear niche (weather via wttr.in/Open-Meteo) with distinct triggers and an explicit NOT-for list (historical data, severe alerts, meteorological analysis) makes conflict with other skills unlikely, matching the level-3 anchor.

3 / 3

Total

11

/

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
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.