AB flight-risk-assessment-frat
Use this skill when a pilot-in-command, dispatcher, chief pilot, or flight-school instructor needs to run a pre-flight FRAT for a Part 91, 135, 137, or 141 operation. Walks PAVE + IMSAFE, scores each category, maps to Green/Yellow/Red, and produces a DRAFT FRAT log with mitigation plan and dispatch recommendation. Go/no-go decision remains the PIC's.
As a process B 76/100 · Nearly there — weak spots: when it triggers, running it twice
How to improve
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 76/100
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 6 mutating operations with no state check
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Failures and branches. 4 branches
- 100Tools and files. No external tools needed
- 100Steps. 59 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3679 tokens
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +1No license
- +2Single-language instructions
- +3Description length 352: enough signal without eating the budget
- +4Structure: 22 headings
- +3Step-by-step instructions: 59 items
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.