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.
97
Does it follow best practices?
Validation for skill structure
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 specifies concrete capabilities with named services, includes natural trigger terms users would actually say, explicitly states both when to use and when NOT to use the skill, and carves out a distinct niche. The 'No API key needed' note adds helpful implementation context.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists specific concrete actions: 'Get current weather and forecasts' with named services 'wttr.in or Open-Meteo'. Also specifies what it does NOT do, adding clarity. | 3 / 3 |
Completeness | Clearly 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'). Also includes explicit NOT for clause defining boundaries. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'weather', 'temperature', 'forecasts', 'location'. These are common terms users naturally use when asking about weather. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche with distinct triggers around weather/temperature/forecasts. The 'NOT for' clause explicitly excludes historical data and severe alerts, reducing conflict with potential related skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill that exemplifies good design: concise, actionable, and well-structured. It provides executable commands for all common weather queries without unnecessary explanation, respects Claude's intelligence, and organizes content logically from simple to complex use cases.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, providing only actionable commands without explaining what weather is or how curl works. Every section serves a clear purpose with no padding. | 3 / 3 |
Actionability | Fully executable curl commands throughout, copy-paste ready with clear examples for different use cases. Format codes are documented concisely for customization. | 3 / 3 |
Workflow Clarity | This is a simple, single-task skill (fetching weather data) with no multi-step process requiring validation. The commands are unambiguous and self-contained. | 3 / 3 |
Progressive Disclosure | Well-organized sections progress logically from basic to advanced usage. For a skill under 50 lines with no need for external references, the structure is appropriate and easy to navigate. | 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.
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 | |
- 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.