BC agent-assistant-pro
Agent身份助手专业版是面向团队与企业的Agent人格治理平台，在免费版三层身份模型的基础上，新增多人格矩阵管理、跨场景自适应切换、企业级合规审计、人格A/B测试框架与团队协作能力。核心能力：支持同时管理20+个Agent人格卡，根据对话上下文自动切换基调；生成价值观一致性审计报告；提供人格对比测试框架，量化不同人格在转化率、满意度上的差异；支持团队级人格库共享与权限管理 功能涵盖: assistant。
Agent身份助手专业版是面向团队与企业的Agent人格治理平台，在免费版三层身份模型的基础上，新增多人格矩阵管理、跨场景自适应切换、企业级合规审计、人格A/B测试框架与团队协作能力。核心能力：支持同时管理20+个Agent人格卡，根据对话上下文自动切换基调；生成价值观一致性审计报告；提供人格对比测试框架，量化不同人…
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: 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 8, column 14: description: Agent身份助手专业版是面向团队与企业的Agent人格治理平台，在免费版三层身份模型的基础上，新增多人格矩阵管理、跨场景自适应切换… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
description-long-hermesdescription is 205 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"
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. 69 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2813 tokens
- 100Running it twice. No mutating operations
- low 20 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 205: enough signal without eating the budget
- +4Structure: 67 headings
- +3Step-by-step instructions: 69 items
- +4Has examples (10 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 54.