AB meeting-debrief
Process meeting transcripts to extract action items, recommendations, key topics, relationships, and generate Excalidraw visualizations. Use when the user shares a meeting transcript, recording notes, or conversation summary and wants a structured debrief with visual output.
As a process B 73/100 · Nearly there — weak spots: result and completion, 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: 3. 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 73/100
- 0Result and completion. Does not say what the result is
- 30Running it twice. 3 mutating operations with no state check
- 65Failures and branches. 3 branches
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. No external tools needed
- 100Steps. 45 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1160 tokens
- 100Progress reporting. Reports progress
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)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 275: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 45 items
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.