BC meeting-notes
Generate structured meeting minutes from transcripts or raw notes — extract key decisions, action items, and follow-ups. Use when the user needs to: (1) convert meeting recordings or transcripts into formatted notes, (2) extract decisions and owners from informal discussion, (3) track task assignments across multiple meetings, (4) produce meeting summaries for distribution, (5) archive meeting records for later reference. Supports 1:1s, team standups, client meetings, technical design reviews, and board/project steering meetings.
Generate structured meeting minutes from transcripts or raw notes — extract key decisions, action items, and follow-ups.
As a process C 58/100 · Has gaps — weak spots: result and completion, inputs and preconditions, consistency
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: Generate structured meeting minutes from transcripts or raw notes … ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - note
frontmatter-keyunknown frontmatter key "emoji"
Process rating: all ten parameters 58/100
- 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
- 30Running it twice. 1 mutating operations with no state check
- 40Consistency. Frontmatter name (meeting-notes) differs from the folder (zcx-meeting-notes)
- 65Failures and branches. 3 branches
- 70When it triggers. States when to use, but not when not to
- 100Tools and files. No external tools needed
- 100Steps. 22 steps
- 100Execution cost. Instruction body is 1268 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
- +1No license
- +2Single-language instructions
- +3Description length 535: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 22 items
- +4Has examples (6 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 73.