ligolnik/flight-weather-watch
Aviation weather briefing tool that fetches WPC prog charts, QPF, and AWC products, overlays flight routes, and generates HTML briefings with Claude analysis.
45
90%
Does it follow best practices?
Impact
0%
0.00xAverage score across 6 eval scenarios
Advisory
Suggest reviewing before use
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 clearly defines a specialized aviation weather briefing capability. It uses third person voice, lists concrete actions and data sources, includes a well-crafted 'Use when' clause with natural trigger terms pilots would use, and occupies a highly distinctive niche that minimizes conflict risk with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: fetches WPC prog charts, QPF, AWC icing/turbulence/SIGMET charts, overlays the flight route, and produces a self-contained HTML briefing. These are highly specific, domain-appropriate capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (generates aviation weather briefing with prog charts, QPF, icing/turbulence/SIGMET charts, route overlay, HTML output) and 'when' (explicit 'Use when' clause listing weather briefing, preflight weather, go/no-go assessment, route weather analysis). | 3 / 3 |
Trigger Term Quality | Includes excellent natural trigger terms users would say: 'weather briefing', 'preflight weather', 'go/no-go assessment', 'route weather analysis', 'VFR/IFR flight'. These cover the main ways a pilot would phrase such a request. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche combining aviation, weather briefing, specific chart types (WPC prog, QPF, AWC), and flight route analysis. Very unlikely to conflict with other skills due to the specialized aviation domain. | 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 well-crafted skill with strong actionability and workflow clarity. The CLI command syntax, options, and workflow steps are concrete and executable, with thorough validation checkpoints including subtle checks like time-window alignment. The main weakness is moderate verbosity — some sections could be tightened, and the skill carries a fair amount of inline detail that could benefit from being split into reference files.
Suggestions
Trim the 'Use When' section to 2-3 key triggers instead of 5 bullets plus negative examples — Claude can generalize from fewer examples.
Consider moving the detailed validation sub-checks (time-window alignment, factual values) and error handling into a separate reference file to keep the main skill leaner.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient and well-structured, but includes some content that could be tightened — e.g., the 'Use When' section is somewhat verbose with many bullet examples, and the 'Interpreting User Requests' section explains things Claude could infer. The validation step 4 is quite detailed but arguably necessary given the complexity of the task. | 2 / 3 |
Actionability | Provides fully executable CLI commands with clear positional arguments, options table, and concrete examples including the cache rebuild command. The workflow is specific with exact flags, file naming conventions, and error messages to look for. | 3 / 3 |
Workflow Clarity | The 5-step workflow is clearly sequenced with explicit validation checkpoints (exit code, HTML creation, chart fetch summary, GO/NO-GO recommendation, time-window alignment, factual values). Includes error recovery guidance and a separate re-run-from-cache workflow with verification steps. | 3 / 3 |
Progressive Disclosure | References reference.md for airport codes and timezone conversion, which is good. However, the skill is fairly long (~120 lines of content) and some sections like the detailed validation checks in step 4 or the error handling section could potentially be split into a separate reference file. The structure is reasonable but the single file carries a lot of detail. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
Reviewed
Table of Contents