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
Quality
100%
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 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 is a helpful implementation detail.
| 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 cases, adding boundary clarity. | 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 explicit 'NOT for' clause (historical data, severe alerts, meteorological analysis) further reduces conflict risk 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 file that demonstrates strong conciseness and actionability. It provides immediately executable curl commands organized by common use cases, includes helpful format codes for customization, and clearly defines scope boundaries. The structure is clean and navigable without unnecessary explanation.
| 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 | All examples are fully executable curl commands that can be copy-pasted directly. Format codes, unit options, and specific use cases are all concrete and immediately usable. | 3 / 3 |
Workflow Clarity | This is a simple, single-task skill (fetching weather data) with no multi-step processes requiring validation. The commands are unambiguous and the organization by use case (current, forecast, format) is clear. | 3 / 3 |
Progressive Disclosure | Content is well-organized into logical sections (when to use, commands, quick responses, notes) without being monolithic. For a self-contained skill of this scope, no external references are needed. | 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 | |
8763418
Table of Contents
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.