BF meeting-analyzer
会议逐字稿精细化分析工具：输入腾讯会议或飞书会议链接，输出结构化分析 JSON（阶段/关键点/决策/待办/参与者画像）、drawio 概要图与 Markdown/HTML 报告。当用户要分析会议逐字稿、生成会议纪要可视化、提取会议关键内容截图、制作会议总结网页时使用。
会议逐字稿精细化分析工具：输入腾讯会议或飞书会议链接，输出结构化分析 JSON（阶段/关键点/决策/待办/参与者画像）、drawio 概要图与 Markdown/HTML 报告。当用户要分析会议逐字稿、生成会议纪要可视化、提取会议关键内容截图、制作会议总结网页时使用。
As a process F 35/100 · Will not run — References files that are not bundled: scripts/src/schemas/meeting.ts
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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: 0. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
missing-refreference to a missing file: scripts/src/schemas/meeting.ts - note
frontmatter-keyunknown frontmatter key "slug" - note
frontmatter-keyunknown frontmatter key "displayName" - note
frontmatter-keyunknown frontmatter key "summary" - note
frontmatter-keyunknown frontmatter key "icon" - note
frontmatter-keyunknown frontmatter key "iconMono" - note
frontmatter-keyunknown frontmatter key "brandColor" - note
frontmatter-keyunknown frontmatter key "homepage" - note
frontmatter-keyunknown frontmatter key "repository" - note
frontmatter-keyunknown frontmatter key "keywords"
Process rating: all ten parameters 35/100
- 0Tools and files. 1 referenced file(s) missing: scripts/src/schemas/meeting.ts
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 100Steps. 13 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 720 tokens
- 100Running it twice. No mutating operations
- low The response is described with custom markup (4 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
- +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
- +2Single-language instructions
- +3Description length 134: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 13 items
- +4Has examples (2 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 64.