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 marks. It concisely states what it does, when to use it, and importantly what it does NOT cover, making it easy for Claude to select or reject this skill. The use of third person voice, natural trigger terms, and explicit boundary conditions make it a model description.
| 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' (user asks about weather, temperature, or forecasts for any location), with explicit 'Use when' and 'NOT for' clauses providing clear trigger and boundary guidance. | 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 | Highly distinctive with a clear niche (weather data retrieval), specific tool names (wttr.in, Open-Meteo), and explicit exclusions (historical data, severe alerts, detailed meteorological analysis) that clearly delineate boundaries from potentially overlapping 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.
This is a solid, actionable skill with concrete curl commands covering the main weather query patterns. Its main weakness is mild verbosity in the use/don't-use sections and the mismatch between the description (mentioning Open-Meteo) and the content (only covering wttr.in). The structure is clear and the commands are immediately executable.
Suggestions
Trim the 'When to Use' and 'When NOT to Use' sections to a compact list—Claude can infer appropriate usage from the skill description without example user phrases.
Either add Open-Meteo as a fallback option (as promised in the description) or remove it from the description to avoid a content mismatch.
| 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 add value, but the overall content could be tightened—e.g., Claude doesn't need example user phrases like 'What's the weather?' spelled out. | 2 / 3 |
Actionability | Every section provides concrete, copy-paste-ready curl commands with specific URLs and format strings. The format codes table and multiple usage patterns give Claude everything needed to construct appropriate requests. | 3 / 3 |
Workflow Clarity | This is a simple, single-purpose skill (run a curl command, return results). There are no destructive or batch operations requiring validation checkpoints. The commands are unambiguous and the different use cases (current, forecast, format options) are clearly separated. | 3 / 3 |
Progressive Disclosure | The content is well-organized with clear section headers, but it's somewhat long for a single-file skill. The description mentions Open-Meteo as an alternative API but the content only covers wttr.in—either the description should be updated or Open-Meteo guidance could be in a separate reference file. The content is all inline but reasonably structured. | 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
- qsimeon/openclaw-engaging
- Commit
4467e04
- 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.