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
{
"context": "Tests whether the agent correctly resolves Nashville and Austin to the user's preferred ICAO codes (KMQY and KEDC), converts local Central Daylight Time to UTC, uses the correct CLI argument format, and always includes the --cache flag.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Nashville as KMQY",
"description": "Uses KMQY as the origin airport code (not KBNA, BNA, or any other Nashville code)",
"max_score": 20
},
{
"name": "Austin as KEDC",
"description": "Uses KEDC as the destination airport code (not KAUS, AUS, or any other Austin code)",
"max_score": 20
},
{
"name": "Cache flag included",
"description": "Includes the --cache flag in the flightweather.py command",
"max_score": 20
},
{
"name": "Correct UTC time",
"description": "Departure time converted to 14:00 UTC (9 AM CDT = UTC-5, so 09:00 + 05:00 = 14:00)",
"max_score": 15
},
{
"name": "Correct date format",
"description": "Date argument is formatted as YYYY-MM-DD (i.e., 2026-03-28)",
"max_score": 10
},
{
"name": "Correct altitude format",
"description": "Altitude passed as an integer (9500), not a string or float",
"max_score": 5
},
{
"name": "TAS flag used",
"description": "Includes --tas 145 to specify the aircraft's true airspeed",
"max_score": 5
},
{
"name": "Correct argument order",
"description": "Command follows the positional order: ORIGIN DESTINATION DATE TIME_UTC ALTITUDE_FT [options]",
"max_score": 5
}
]
}.tessl-plugin
evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
skills
flight-weather