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.

72

Quality

92%

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.

This is a well-structured, highly actionable weather skill with concrete, executable curl commands covering the main use cases. The main weakness is mild verbosity in the 'When to Use' / 'When NOT to Use' sections, which enumerate obvious trigger phrases and alternatives that Claude can infer. Overall it's a solid, practical skill that efficiently teaches Claude how to fetch weather data.

Suggestions

Condense the 'When to Use' and 'When NOT to Use' sections into a brief 1-2 line summary each, since Claude can infer weather-related intent without explicit trigger phrase examples.

DimensionReasoningScore

Conciseness

The 'When to Use' and 'When NOT to Use' sections are somewhat verbose for Claude's capabilities—Claude doesn't need trigger phrase examples listed out. The format codes reference and command examples are efficient, but the overall document could be tightened by removing the obvious use-case enumeration.

2 / 3

Actionability

All commands are fully executable curl commands with concrete examples for different scenarios (current weather, forecasts, specific formats). The format codes table and quick response templates are copy-paste ready.

3 / 3

Workflow Clarity

This is a simple, single-task skill (run a curl command and return results). There are no multi-step processes or destructive operations requiring validation checkpoints. The commands are clearly categorized and unambiguous.

3 / 3

Progressive Disclosure

For a simple skill under ~80 lines with no need for external references, the content is well-organized into logical sections (commands, format options, quick responses, notes). No bundle files are needed and the structure supports easy navigation.

3 / 3

Total

11

/

12

Passed

Description

100%

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

This is an excellent skill description that clearly communicates what the skill does, when to use it, and importantly, when NOT to use it. It uses natural trigger terms, names specific tools/APIs, and has a well-defined scope that minimizes conflict with other skills. The inclusion of 'No API key needed' is a helpful practical detail.

DimensionReasoningScore

Specificity

Lists specific concrete actions: 'Get current weather and forecasts', names specific services 'wttr.in or Open-Meteo', and explicitly states 'No API key needed'. Also clearly scopes out what it doesn't do.

3 / 3

Completeness

Clearly answers both 'what' (get current weather and forecasts via wttr.in or Open-Meteo) and 'when' (explicit 'Use when: user asks about weather, temperature, or forecasts for any location'). Also includes a 'NOT for' clause that further clarifies boundaries.

3 / 3

Trigger Term Quality

Includes natural keywords users would say: 'weather', 'temperature', 'forecasts', 'location'. These are exactly the terms a user would use when asking about weather conditions.

3 / 3

Distinctiveness Conflict Risk

Very distinct niche — weather data retrieval via specific APIs. The 'NOT for' clause (historical data, severe alerts, meteorological analysis) further reduces conflict risk with any adjacent skills. Unlikely to be confused with other skills.

3 / 3

Total

12

/

12

Passed

Validation

72%

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

Validation8 / 11 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

8

/

11

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.