BC xiaozhi-english-speaking-coach
英语口语陪练：陪你开口说，说完再一起复盘；在你允许时记住发音弱点。触发语（须含明确的练习意图）："练口语"、"帮我练英语对话"、"我英语不敢开口"、"角色扮演"、"即兴演讲"、"帮我纠音"、"开始晨间热身"、"做口语复盘"。不触发：日常语音消息里夹带英语、"Good morning" 等普通问候、查单词、翻译句子——按普通对话回答即可，不进入练习流程，也不读写口语档案。核心工作流：晨间 5 分钟热身（打开→开场→聊天→复盘→存档）+ 三种训练场景（角色扮演/即兴演讲/纠音闭环）+ 四级追问 + 口语档案（经同意后才建立）。不处理：整篇作文批改（转英语写作进化教练）、句子语法错误的系统追问（转英语语法突破教练）、单词记忆与到期复习（转智能词汇DNA系统）。
英语口语陪练：陪你开口说，说完再一起复盘；在你允许时记住发音弱点。触发语（须含明确的练习意图）："练口语"、"帮我练英语对话"、"我英语不敢开口"、"角色扮演"、"即兴演讲"、"帮我纠音"、"开始晨间热身"、"做口语复盘"。不触发：日常语音消息里夹带英语、"Good morning"…
As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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: 14. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 331 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - warning
description-no-whenneither description nor a "## When to Use" section says when to use the skill - note
frontmatter-keyunknown frontmatter key "display_name" - note
frontmatter-keyunknown frontmatter key "grade_bands" - note
frontmatter-keyunknown frontmatter key "depends_on" - note
frontmatter-keyunknown frontmatter key "slug" - note
frontmatter-keyunknown frontmatter key "displayName" - note
frontmatter-keyunknown frontmatter key "summary"
Process rating: all ten parameters 53/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
- 100Tools and files. No external tools needed
- 100Steps. 21 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2991 tokens
- 100Running it twice. No mutating operations
- low 11 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
- +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
- +5Description quotes 4 example trigger phrases
- +3Description length 331: enough signal without eating the budget
- +4Structure: 29 headings
- +3Step-by-step instructions: 21 items
- +4Has examples (22 code blocks)
- +4Reference files are cited in the instructions (4 of 4)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 73.