weather
Get current weather and forecasts (no API key required).
73
70%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/weather/SKILL.mdQuality
Discovery
40%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description is concise and identifies a clear niche (weather data retrieval) with a useful differentiator (no API key). However, it lacks an explicit 'Use when...' clause and could benefit from more trigger terms and specific capability details to help Claude reliably select it.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about weather, temperature, rain, forecasts, or conditions for a specific location.'
Include more natural trigger terms users might say, such as 'temperature', 'rain', 'snow', 'humidity', 'tomorrow's weather', or 'weather in [city]'.
List more specific capabilities, e.g., 'Retrieves current conditions, multi-day forecasts, temperature, humidity, and wind speed for any location.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (weather) and two actions (current weather and forecasts), plus a notable constraint (no API key required), but doesn't list more specific capabilities like location lookup, multi-day forecasts, or specific data points returned. | 2 / 3 |
Completeness | Describes what it does (get weather and forecasts) but has no explicit 'Use when...' clause or equivalent trigger guidance, which per the rubric should cap completeness at 2, and the 'what' is also fairly thin, placing this at 1. | 1 / 3 |
Trigger Term Quality | Includes 'weather' and 'forecasts' which are natural terms users would say, but misses common variations like 'temperature', 'rain', 'climate', 'tomorrow's weather', or location-based triggers. | 2 / 3 |
Distinctiveness Conflict Risk | Weather is a clear, distinct niche that is unlikely to conflict with other skills. The mention of 'no API key required' further distinguishes it from other potential weather-related skills. | 3 / 3 |
Total | 8 / 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, lean skill that provides immediately actionable weather-fetching commands with no wasted tokens. It smartly offers a primary and fallback service, includes practical tips (URL encoding, units, output formats), and shows expected output for key examples. The structure is clean and appropriately sized for the task's simplicity.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every token earns its place. No unnecessary explanations of what weather APIs are or how curl works. Format codes are presented as a compact reference list. Tips are terse and useful. | 3 / 3 |
Actionability | All examples are fully executable curl commands with expected output shown. Format codes, URL encoding tips, and unit options are concrete and copy-paste ready. | 3 / 3 |
Workflow Clarity | This is a simple, single-purpose skill (fetch weather data). The workflow is unambiguous: run a curl command, get output. Primary and fallback services are clearly distinguished. No multi-step or destructive operations require validation checkpoints. | 3 / 3 |
Progressive Disclosure | For a simple skill under 50 lines with no need for external references, the content is well-organized with clear sections (primary service, fallback, tips). The Open-Meteo docs link provides appropriate one-level-deep reference for advanced use. | 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 | |
- Repository
- deepgram/dglabs-deepclaw
- Commit
ec8d4f8
- 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.