CC apple-health-tool-free
面向个人用户的健康数据查询助手,通过自然语言与 Apple Health 数据交互,可产出提升工作效率. 适用于需要apple health tool相关能力的开发场景,提供结构化的工作流程和配置指引. 该工具经过深度差异化处理,针对用户反馈和使用痛点进行了优化改进,提升了实用性和可操作性.
面向个人用户的健康数据查询助手,通过自然语言与 Apple Health 数据交互,可产出提升工作效率.
As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The instructions or scripts send data out: environment variables, keys, file contents, chat history. You may never notice, because the agent performs the upload as "part of the task".
If the upload is not needed for the task, remove it: catalogs flag such skills and delist them. If it is needed, name the destination explicitly, say what leaves the machine, and give the user a switch.
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 · 4
✓ No critical or high findings
Medium and low: 4
-
medium Exfiltration
net-credential-useSKILL.md:78Credential used in a network call (verify the destination is the intended service)curl -X POST -H "X-API-ref: $TRANSITION_API_KEY" \
-
medium Exfiltration
net-credential-useSKILL.md:97Credential used in a network call (verify the destination is the intended service)curl -X POST -H "X-API-ref: $TRANSITION_API_KEY" \
-
medium Exfiltration
net-credential-useSKILL.md:136Credential used in a network call (verify the destination is the intended service)curl -s -H "X-API-ref: $TRANSITION_API_KEY" \
-
medium Exfiltration
net-credential-useSKILL.md:205Credential used in a network call (verify the destination is the intended service)curl -H "X-API-ref: $TRANSITION_API_KEY" \
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 146 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" - note
frontmatter-keyunknown frontmatter key "pricing_tier"
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. 13 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1611 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
- +2Single-language instructions
- +3Description length 146: enough signal without eating the budget
- +4Structure: 38 headings
- +3Step-by-step instructions: 13 items
- +4Has examples (12 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 64.