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.
88
88%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
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 hits all the key criteria. It concisely states what it does, which services it uses, when to trigger it with natural user terms, and explicitly scopes out what it doesn't handle. The 'NOT for' clause is a particularly strong addition that helps Claude disambiguate this skill from related ones.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists specific concrete actions: 'Get current weather and forecasts', names specific services 'wttr.in or Open-Meteo', and explicitly states what it does NOT do (historical data, severe weather alerts, detailed meteorological analysis). | 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 which adds further clarity on 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 clear niche focused on weather data retrieval with specific service names and explicit exclusions (historical data, severe alerts, meteorological analysis). The 'NOT for' clause actively reduces conflict risk with other potential skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A solid, actionable weather skill with excellent executable examples covering common use cases. The main weaknesses are mild verbosity in the when-to-use/not-use sections (which Claude can infer) and the missing Open-Meteo fallback mentioned in the description. Overall well-organized and practical.
Suggestions
Remove or significantly trim the 'When to Use' trigger phrases — Claude can infer these from the skill description and doesn't need example user messages.
Add Open-Meteo as a fallback option since it's mentioned in the skill description but absent from the content.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The 'When to Use' and 'When NOT to Use' sections are somewhat verbose and repeat information already in the frontmatter description. The format codes reference and multiple example variations add some bulk, but most content is useful. The skill could be tightened by removing the trigger phrase examples Claude doesn't need. | 2 / 3 |
Actionability | Every section provides concrete, copy-paste ready curl commands with clear parameter explanations. The format codes, unit options, and quick response templates are all directly executable. | 3 / 3 |
Workflow Clarity | This is a simple, single-purpose skill (run a curl command, get weather). There's no multi-step destructive process requiring validation checkpoints. The commands are unambiguous and well-organized by use case (current, forecast, format options). | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear headers, but everything is inline in a single file. The format codes table and quick responses section could potentially be separated, though for a skill of this size (~80 lines of content) it's borderline acceptable. The description mentions Open-Meteo as an alternative but no reference or fallback instructions are provided. | 2 / 3 |
Total | 10 / 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.
Validation — 8 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
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
- Commit
0c1ec2b
- 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.