BD join-meeting
|-。会议机器人，支持会议感知、系统状态管理、生命周期、语音状态与TTS事件处理。智能会议机器人，主动感知并参与在线会议. 支持会议感知、系统状态管理、生命周期管理（加入/离开）。Use when 需要项目管理、任务规划、进度跟踪、团队协作时使用。不适用于实际人员绩效评估。适用于独立开发者、企业团队和自动化工作流场景。 功能涵盖: join, meeting。
|-。会议机器人，支持会议感知、系统状态管理、生命周期、语音状态与TTS事件处理。智能会议机器人，主动感知并参与在线会议.
As a process D 49/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
The same skill appears in 1 more place: ClawHub
How to improve
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
- 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: Block scalar header includes extra characters: |-。会议机器人，支持会议感知、系统状态管理、生命周期、语音状态与TTS事件处理。智能会议机器人，主动感知并参与在线会议. at line 11, column 16: description: |-。会议机器人，支持会议感知、系统状态管理、生命周期、语音状态与TTS事件处理。智能会议机器人，主动感知并参与在线会议. 支持会议… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
description-long-hermesdescription is 181 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - note
frontmatter-keyunknown frontmatter key "slug" - note
frontmatter-keyunknown frontmatter key "displayName" - note
frontmatter-keyunknown frontmatter key "summary" - note
frontmatter-keyunknown frontmatter key "summary_zh" - note
frontmatter-keyunknown frontmatter key "tools" - note
frontmatter-keyunknown frontmatter key "pricing_tier"
Process rating: all ten parameters 49/100
- 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
- 40Consistency. Frontmatter name (join-meeting) differs from the folder (meeting-join-2)
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 77 steps
- 100Execution cost. Instruction body is 1578 tokens
- 100Running it twice. No mutating operations
- low 12 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)
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +3Description length 181: enough signal without eating the budget
- +4Structure: 40 headings
- +3Step-by-step instructions: 77 items
- +4Has examples (4 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 66.