AB meeting-prep-agent
Pre-meeting research, agenda generation, talking points, and post-meeting action item capture. Use when preparing for client meetings, internal reviews, board presentations, vendor negotiations, or stakeholder briefings. Produces structured briefs, agendas, and follow-up documents. NOT for: scheduling (use calendar tools), recurring standup notes, or meetings where you have no context on participants or purpose.
As a process B 78/100 · Nearly there — weak spots: consistency, 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: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: Pre-meeting research, agenda generation, talking points, and post-… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
Process rating: all ten parameters 78/100
- 30Running it twice. 2 mutating operations with no state check
- 40Consistency. Frontmatter name (meeting-prep-agent) differs from the folder (pl-meeting-prep)
- 50When it triggers. No condition that starts the skill
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. No external tools needed
- 100Steps. 41 steps
- 100Failures and branches. 2 branches, has a failure section
- 100Execution cost. Instruction body is 1701 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
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 415: enough signal without eating the budget
- +4Structure: 17 headings
- +3Step-by-step instructions: 41 items
- +3Output format is stated explicitly
- +4Has examples (6 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 81.