BC apple-higDesign-skill
Apple 平台设计系统技能。覆盖 Apple Human Interface Guidelines (HIG),包括设计原则 (Hierarchy/Harmony/Consistency)、Typography(San Francisco/Dynamic Type)、 Color System(系统色/Liquid Glass)、SF Symbols(图标库/动画)、Components (Button/Navigation/Tab Bar/Alert/List/TextField/SearchBar/Toggle/DatePicker)、 Accessibility、Dark Mode、Animation、空间布局(visionOS)、Branding。 当用户提到 Apple 设计、iOS UI 规范、Apple HIG、iOS 设计语言、SF Symbols、 Dark Mode 设计、visionOS 空间 UI 时触发。
As a process C 56/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: 18. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - note
frontmatter-keyunknown frontmatter key "trigger" - note
frontmatter-keyunknown frontmatter key "hermes"
Process rating: all ten parameters 56/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 2 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 100Tools and files. No external tools needed
- 100Steps. 148 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3893 tokens
- 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
- -250 emoji in the instructions: noise for the model
- -415 reference files, but SKILL.md never points to them: the model will not open them
- +2Single-language instructions
- +3Description length 422: enough signal without eating the budget
- +4Structure: 115 headings
- +3Step-by-step instructions: 148 items
- +4Has examples (10 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 60.