BF medxpert-content-ops
MedXpert 官网与内容运营规范（定稿）。覆盖官网视觉规范 v2（浅蓝家族）、AI 友好隐藏原则、内容原则、乐享→官网同步流程与关键路径、整站改版纪律与页面产出检查清单。触发场景：MedXpert 官网（medxpert.cn）视觉/配色、官网内容更新、公众号话术、官网同步、乐享内容同步、对外宣传文案、SEO/AI 索引（llms.txt/sitemap/JSON-LD）。当用户说「官网配色怎么定」「公众号话术」「官网和乐享怎么同步」「内容要符合什么规范」「AI 索引/llms.txt 怎么配」时加载本技能，即获当前定稿规范，避免重复摸索或误用旧版。
MedXpert 官网与内容运营规范（定稿）。覆盖官网视觉规范 v2（浅蓝家族）、AI 友好隐藏原则、内容原则、乐享→官网同步流程与关键路径、整站改版纪律与页面产出检查清单。触发场景：MedXpert…
As a process F 35/100 · Will not run — References files that are not bundled: assets/logo.png
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.
- 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: 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: Nested mappings are not allowed in compact mappings at line 7, column 17: description_en: MedXpert official-site & content-ops standard (final): v2 visua… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
description-long-hermesdescription is 280 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 - warning
missing-refreference to a missing file: assets/logo.png - note
frontmatter-keyunknown frontmatter key "title" - note
frontmatter-keyunknown frontmatter key "displayName" - note
frontmatter-keyunknown frontmatter key "display_name" - note
frontmatter-keyunknown frontmatter key "description_zh" - note
frontmatter-keyunknown frontmatter key "description_en" - note
frontmatter-keyunknown frontmatter key "xiaping_category" - note
frontmatter-keyunknown frontmatter key "xiaping_tags" - note
frontmatter-keyunknown frontmatter key "agent_created"
Process rating: all ten parameters 35/100
- 0Tools and files. 1 referenced file(s) missing: assets/logo.png
- 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. 53 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 891 tokens
- 100Running it twice. No mutating operations
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 280: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 53 items
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 44.