weather
Get current weather and forecasts (no API key required).
78
Quality
70%
Does it follow best practices?
Impact
100%
1.19xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./nanobot/skills/weather/SKILL.mdDiscovery
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 identifies a clear domain (weather) with reasonable specificity but fails to include explicit trigger guidance, which is critical for skill selection. The parenthetical about no API key is helpful for distinctiveness but doesn't compensate for missing 'Use when' triggers and limited keyword coverage.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user asks about weather, temperature, rain, forecasts, or conditions for a location.'
Expand trigger terms to include natural variations users would say: 'temperature', 'rain', 'sunny', 'tomorrow's weather', 'weekly forecast', 'weather in [city]'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (weather) and two actions (current weather, forecasts), but lacks comprehensive detail about specific capabilities like temperature units, location types, or forecast duration. | 2 / 3 |
Completeness | Describes what it does (get weather/forecasts) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes natural terms 'weather' and 'forecasts' that users would say, but misses common variations like 'temperature', 'rain', 'tomorrow's weather', 'hourly forecast', or location-based triggers. | 2 / 3 |
Distinctiveness Conflict Risk | Weather is a clear, distinct niche that is unlikely to conflict with other skills. The parenthetical about no API key adds useful distinguishing context. | 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, well-crafted skill that exemplifies token efficiency and actionability. It provides two complete, working solutions with executable examples, clear format references, and practical tips - all in minimal space. The structure is clean and the content assumes Claude's competence without over-explaining.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No unnecessary explanations of what weather APIs are or how curl works. Every line provides actionable information - format codes, tips, and examples are all directly useful. | 3 / 3 |
Actionability | Fully executable curl commands that are copy-paste ready. Includes concrete output examples showing exactly what to expect. Format codes and tips provide specific, actionable guidance for customization. | 3 / 3 |
Workflow Clarity | This is a simple, single-purpose skill with no multi-step destructive operations. The single action (making a curl request) is completely unambiguous, and the fallback service is clearly labeled as such. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections (primary service, fallback). For a skill under 50 lines with no need for external references, the structure is appropriate. External docs link provided for deeper exploration. | 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.