BF foundation-meeting-synthesize
Cross-meeting archaeology skill. Consumes multiple meeting recaps (or raw notes) over a period and surfaces patterns invisible in any single meeting. Shows how decisions evolved, who has been saying what, where threads are stalling, and where contradictions have emerged. Produces a plain-text timeline, themes with confidence markers, stakeholder position tracking, consolidated decision list, contradiction flags, open items, narrative summary, and prioritized follow-ups.
Cross-meeting archaeology skill.
As a process F 36/100 · Will not run — References files that are not bundled: ../../docs/reference/skill-families/meeting-skills-contract.md, ../foundation-meeting-recap/SKILL.md, ../discover-interview-synthesis/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-recap/SKILL.md - warning
missing-refreference to a missing file: ../discover-interview-synthesis/SKILL.md
Process rating: all ten parameters 36/100
- 0Tools and files. 3 referenced file(s) missing: ../../docs/reference/skill-families/meeting-skills-contract.md, ../foundation-meeting-recap/SKILL.md, ../discover-interview-synthesis/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
- 60Failures and branches. 2 branches
- 85Steps. 49 steps, 1 vague phrases
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2204 tokens
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 474: enough signal without eating the budget
- +4Structure: 8 headings
- +3Step-by-step instructions: 49 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.