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
88%
1.39xAverage score across 3 eval scenarios
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 marks. It concisely states what it does, which tools it uses, when to trigger it, and what it explicitly excludes—all in third person voice. The inclusion of both positive triggers and negative boundaries makes it highly effective for skill selection among many options.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists specific concrete actions: 'Get current weather and forecasts', names specific tools/APIs ('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' clause with triggers). Also includes a 'NOT for' clause that further clarifies boundaries, and notes no API key is needed. | 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 | Clearly scoped to weather queries with specific API sources named. The 'NOT for' exclusions (historical data, severe alerts, meteorological analysis) further reduce conflict risk with any related but different 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 concrete curl commands covering the main use cases. Its primary weakness is mild verbosity—the 'When to Use/Not Use' sections and the 'Quick Responses' section partially duplicate other content. The skill could be tightened by removing redundant sections and trusting Claude to compose commands from the format codes and base patterns.
Suggestions
Remove or significantly trim the 'When to Use' section—Claude can infer weather-related intent without example user phrases.
Merge 'Quick Responses' into the 'Commands' section or remove it, since it largely repeats the same curl patterns with minor format string variations.
| 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 quick responses sections are useful but the overall content could be tightened—e.g., Claude doesn't need example user phrases like 'What's the weather?' as trigger examples. | 2 / 3 |
Actionability | Every section provides concrete, copy-paste ready curl commands with real examples. Format codes are clearly listed, and multiple use cases (current weather, forecasts, specific formats, JSON output) are covered with executable commands. | 3 / 3 |
Workflow Clarity | This is a simple, single-purpose skill (fetch weather data via curl). There are no destructive or batch operations requiring validation checkpoints. The commands are clearly categorized by use case (current, forecast, format options), making the workflow unambiguous. | 3 / 3 |
Progressive Disclosure | The content is well-organized with clear section headers, but it's all inline in one file. The format codes, quick responses, and detailed format options could potentially be split out. However, for a skill of this size (~80 lines of content), it's borderline acceptable—the main issue is that some sections feel redundant (Quick Responses largely repeats Commands with slight variations). | 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
- attilaczudor/Test
- Commit
b4fc4af
- 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.