Content
75%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 delivers fully executable, example-driven guidance for both quick lookups and programmatic JSON access, but it is undermined by an irrelevant Setup section that instructs credential export for an API key that no command uses, directly contradicting the skill's 'no API key required' premise. Removing that block and clarifying the primary/secondary service choice would make this a clean, compact skill.
Suggestions
Delete the gooseworks Setup section (or move it behind a clear conditional): its exported GOOSEWORKS_API_KEY/Bearer auth is never used by any command and contradicts the description's 'no API key required' claim.
State the service-selection rule up front in one line, e.g. 'Use wttr.in for human-readable output; use Open-Meteo when you need JSON or coordinates', so the primary/alternative split is explicit.
Consider moving the format-code table, tips, and Examples section into a references/ file (e.g. references/wttr-in-codes.md) to keep SKILL.md as a lean overview.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The curl examples are lean, but the ~10-line Setup block exporting GOOSEWORKS credentials is entirely unnecessary — it contradicts 'no API key required' and no command in the skill ever uses those variables or the Bearer auth header. This is more than a minor trim (anchor 4) though only one padded section rather than several (anchor 2). | 3 / 5 |
Actionability | Every command is copy-paste executable with expected output shown (e.g. '# Output: London: ⛅️ +8°C'), format codes are tabulated, and the Examples section covers the common cases: quick check, multi-day forecast, and JSON-by-coordinates — a clear anchor 5 match. | 5 / 5 |
Workflow Clarity | The single action is largely unambiguous with a primary service (wttr.in), a clearly-signaled JSON alternative, and the geocoding-first step shown. However, the contradictory unused Setup section creates real ambiguity about whether auth is required, holding it below the simple-skill ceiling of 5. | 4 / 5 |
Progressive Disclosure | Sections are well-organized with clear headers and no buried references, and no bundle files are needed at this scale. But the body exceeds the under-50-line simple-skill exception and inlines the format-code table, tips, and examples that could sit in a reference file — good structure with minor organization gaps, anchor 4. | 4 / 5 |
Total | 16 / 20 Passed |