AB proof-meeting-prep
Walk into a B2B call knowing every person in the room. Give it the company, the people on the call, and what you're selling — it researches each stakeholder's role priorities and likely objections from public sources, then proposes the single proof angle that lands for each person, plus how to sequence the room. Use when someone has a live deal and a multi-stakeholder call coming up. Runs standalone on web search + fetch; grounds in your GrowthNation customer proof via MCP when connected.
Walk into a B2B call knowing every person in the room.
As a process B 65/100 · Nearly there — weak spots: when it triggers, running it twice, progress reporting
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
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 65/100
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 3 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 33 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2821 tokens
- 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 493: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 33 items
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.