BC font-manager-pro
字体管理器专业版面向专业前端团队与设计系统的字体排版治理场景，在免费版基础上扩展全功能管理能力。解决专业排版的"系统化与合规"痛点：设计系统需要统一的字体变量管理、多语言页面需要CJK字体适配、无障碍合规要求对比度与字号达标、字体加载需要CDN多级fallback、字体子集化需要自动化工具、排版审计需要可导出的报告
字体管理器专业版面向专业前端团队与设计系统的字体排版治理场景，在免费版基础上扩展全功能管理能力。解决专业排版的"系统化与合规"痛点：设计系统需要统一的字体变量管理、多语言页面需要CJK字体适配、无障碍合规要求对比度与字号达标、字体加载需要CDN多级fallback、字体子集化需要自动化工具、排版审计需要可导出的报告
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: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 158 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 "summary" - note
frontmatter-keyunknown frontmatter key "edition" - note
frontmatter-keyunknown frontmatter key "tools" - note
frontmatter-keyunknown frontmatter key "homepage"
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. Tools declared in frontmatter
- 100Steps. 58 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2823 tokens
- 100Running it twice. No mutating operations
- low 21 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 158: enough signal without eating the budget
- +4Structure: 51 headings
- +3Step-by-step instructions: 58 items
- +4Has examples (14 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 68.