Content
92%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is an exemplary lean skill: every command is executable, expected outputs are shown, format codes and tips are compressed into scannable one-liners, and the primary/fallback service split is clearly signaled. The only weakness is the Open-Meteo fallback's unspecified geocoding step. Well under 50 lines, it needs no bundle files.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and dense: copy-paste commands, expected outputs, a one-line format-code table, and terse tips, with no padding or explanation of concepts Claude already knows. | 5 / 5 |
Actionability | Fully executable curl one-liners with sample outputs cover the common cases, but the Open-Meteo fallback's "Find coordinates for a city, then query" gives no concrete geocoding method, leaving that section a minor gap short of copy-paste ready. | 4 / 5 |
Workflow Clarity | This is a simple single-purpose skill where the primary action (curl wttr.in/<location>) is unambiguous, the primary/fallback split is explicitly labeled, and no destructive or batch operations require validation checkpoints. | 5 / 5 |
Progressive Disclosure | Under 50 lines with no need for external reference files; the two well-signaled sections (wttr.in primary, Open-Meteo fallback) plus a docs link give clean, flat navigation, which the simple-skill guideline scores at 5. | 5 / 5 |
Total | 19 / 20 Passed |