BC meeting-minutes-taker
Transforms raw meeting transcripts into structured, evidence-based meeting minutes — merges multiple versions without losing content, reviews existing minutes against the transcript for missing items, and identifies anonymous speakers (Speaker 1/2/3, 发言人1). Triggers on 会议纪要, 会议记录, 整理纪要, 妙记转纪要, "write meeting minutes", "merge these minutes". Not for fixing ASR/STT errors first (use transcript-fixer).
Transforms raw meeting transcripts into structured, evidence-based meeting minutes — merges multiple versions without losing content, reviews existing minutes…
As a process C 51/100 · Has gaps — References files that are not bundled: meeting-media/..., reviewed-document
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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
body-longSKILL.md body ≈ 9675 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: meeting-media/... - warning
missing-refreference to a missing file: reviewed-document
Process rating: all ten parameters 51/100
- 0Tools and files. 2 referenced file(s) missing: meeting-media/..., reviewed-document
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 9 mutating operations with no state check
- 40Execution cost. Instruction body is 9675 tokens: crowds the task out of the window
- 60Steps. 179 steps, 6 vague phrases
- 60Result and completion. Output format stated, no completion criterion
- 100When it triggers. States when to use and when not to
- 100Failures and branches. 4 branches, has a failure section
- 100Consistency. Name and required fields are in place
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low The response is described with custom markup (6 tags): a typed call is more reliable
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
- -236 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +5Description quotes 2 example trigger phrases
- +4Description says when NOT to use the skill
- +3Description length 402: enough signal without eating the budget
- +4Structure: 42 headings
- +3Step-by-step instructions: 179 items
- +3Output format is stated explicitly
- +4Has examples (23 code blocks)
- +4Reference files are cited in the instructions (3 of 3)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 79.