BF foundation-meeting-recap
Produces a topic-segmented post-meeting summary for attendees with decisions highlighted and actions captured inline per topic (plus a consolidated action view at the end). Auto-populates topic skeleton from a sibling meeting-agenda when available and reconciles planned vs. actual topics. Accepts transcripts from Zoom, Meet, Otter, Fireflies, Krisp MCP, or manual notes; runs on variable-quality input without blocking. For synthesizing user research interviews across participants, use discover-interview-synthesis.
Produces a topic-segmented post-meeting summary for attendees with decisions highlighted and actions captured inline per topic (plus a consolidated action…
As a process F 39/100 · Will not run — References files that are not bundled: ../../docs/reference/skill-families/meeting-skills-contract.md, ../foundation-meeting-agenda/SKILL.md, ../foundation-meeting-synthesize/SKILL.md
How to improve
- The text references files that are not there: add them or drop the references.
- 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
- warning
missing-refreference to a missing file: ../../docs/reference/skill-families/meeting-skills-contract.md - warning
missing-refreference to a missing file: ../foundation-meeting-agenda/SKILL.md - warning
missing-refreference to a missing file: ../foundation-meeting-synthesize/SKILL.md - warning
missing-refreference to a missing file: ../foundation-stakeholder-update/SKILL.md
Process rating: all ten parameters 39/100
- 0Tools and files. 4 referenced file(s) missing: ../../docs/reference/skill-families/meeting-skills-contract.md, ../foundation-meeting-agenda/SKILL.md, ../foundation-meeting-synthesize/SKILL.md
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 2 mutating operations with no state check
- 65Failures and branches. 3 branches
- 100Steps. 59 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2403 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)
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +2Single-language instructions
- +3Description length 518: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 59 items
- +4Reference files are cited in the instructions (1 of 2)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 73.