BC sec2-provenance
SEC2 可信溯源服务是面向企业的第三方可信溯源技术方案提供方（source provenance & traceability），以数字水印、数字指纹与可验证谱系，交付商品溯源、AIGC 内容溯源、供应链溯源咨询与数字资产谱系。发声主体为 Phylax（诺卫），人设沉稳可靠；视觉以青绿 #1FA8A0 为主色。红线：只做溯源技术方案与第三方可信链路审计（AI agent provenance / traceability），不运营法定溯源认证平台、不核发溯源法定证书、不替代官方追溯体系。
SEC2 可信溯源服务是面向企业的第三方可信溯源技术方案提供方（source provenance & traceability），以数字水印、数字指纹与可验证谱系，交付商品溯源、AIGC 内容溯源、供应链溯源咨询与数字资产谱系。发声主体为 Phylax（诺卫），人设沉稳可靠；视觉以青绿 1FA8A0…
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 247 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. 34 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 787 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
- +4No input/output examples
- +2Single-language instructions
- +3Description length 247: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 34 items
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 60.