BB AI Meeting Intelligence Expert
AI-powered meeting intelligence assistant — automatically transcribe, summarize, extract action items, generate follow-ups, and track decisions across your meeting lifecycle. Supports multi-language transcription, speaker identification, sentiment analysis, and integration with calendar/email tools. Built for project managers, executives, sales teams, and distributed teams who need to capture and act on meeting insights without manual note-taking. Keywords: meeting notes, meeting transcription, action items extraction, meeting summary, decision tracking, calendar integration, agenda preparation, meeting efficiency, AI meeting assistant, 会议纪要, 会议转录, 智能摘要, 行动项提取, 会议效率, 待办跟进, 决策追踪.
As a process B 70/100 · Nearly there — weak spots: when it triggers, consistency, running it twice
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 70/100
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 9 mutating operations with no state check
- 40Consistency. Frontmatter name (AI Meeting Intelligence Expert) differs from the folder (ai-meeting-intelligence)
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Execution cost. Instruction body is 4129 tokens
- 100Tools and files. No external tools needed
- 100Steps. 67 steps
- 100Failures and branches. 2 branches, has a failure section
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 13 top-level sections: this looks like several domains in one skill
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 687: enough signal without eating the budget
- +4Structure: 34 headings
- +3Step-by-step instructions: 67 items
- +3Output format is stated explicitly
- +4Has examples (13 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 70.