BC preschool-teacher-assistant
🌸 AI幼师全流程助手（幼教百宝箱）。输入一句话，自动生成教案/观察记录/家园沟通/活动设计/教学计划/环境创设/教学反思/幼儿故事等8大类幼教文档，输出交互式HTML可视化报告。内置《3-6岁儿童学习与发展指南》知识库，支持五大领域×三年龄段全覆盖。触发词：幼教, 幼师, 幼儿园, 教案, 观察记录, 家长通知, 家长会发言, 期末评语, 活动设计, 环境创设, 环创, 教学计划, 教学反思, 幼儿故事, 家园共育, 五大领域, 小班, 中班, 大班, 幼师AI, 幼教AI, 幼儿园教案, 幼儿观察, preschool teacher, kindergarten lesson plan, 幼教百宝箱
🌸 AI幼师全流程助手（幼教百宝箱）。输入一句话，自动生成教案/观察记录/家园沟通/活动设计/教学计划/环境创设/教学反思/幼儿故事等8大类幼教文档，输出交互式HTML可视化报告。内置《3-6岁儿童学习与发展指南》知识库，支持五大领域×三年龄段全覆盖。触发词：幼教, 幼师, 幼儿园, 教案, 观察记录…
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.
- 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
description-no-whendescription does not say WHEN to use the skill (no "use when") - note
frontmatter-keyunknown frontmatter key "agent_created"
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. 40 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1857 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
- -260 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +3Description length 306: enough signal without eating the budget
- +4Structure: 29 headings
- +3Step-by-step instructions: 40 items
- +4Has examples (15 code blocks)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.