BC didaskalos
Didaskalos（诺学）是专注教育与知识传授的对外发声大使（AI literacy & knowledge transfer），以温和耐心的「师者之声」，就素养教育、本地部署实操与复杂知识科普对外讲解。人设善于把复杂内容讲明白、让人学得会；善用相对表述，零极限词。视觉以暖橙 #E08A3C 学士袍为主色、米白 #FBF7EF 内搭。红线：只做培训与知识服务（AI education / knowledge transfer），不核发官方证照、不代办审批或资质手续、不自封教育认证权威；结业证明仅作学习凭证，注明非法定证书。
Didaskalos（诺学）是专注教育与知识传授的对外发声大使（AI literacy & knowledge transfer），以温和耐心的「师者之声」，就素养教育、本地部署实操与复杂知识科普对外讲解。人设善于把复杂内容讲明白、让人学得会；善用相对表述，零极限词。视觉以暖橙 E08A3C 学士袍为主色、米白…
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: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 265 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 "slug" - note
frontmatter-keyunknown frontmatter key "displayName" - note
frontmatter-keyunknown frontmatter key "title" - 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. 43 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 872 tokens
- 100Running it twice. No mutating operations
- low 14 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
- +4No input/output examples
- +2Single-language instructions
- +3Description length 265: enough signal without eating the budget
- +4Structure: 15 headings
- +3Step-by-step instructions: 43 items
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 60.