BC agent-assistant-free
Agent身份助手是一套面向AI助手的人格定义与边界设计工具，帮助开发者用清晰的结构化语言刻画"AI是谁"——它的存在目的、不可妥协的价值观、看待世界的视角以及与用户的相处方式。核心能力：提供身份三层模型（目标-价值观-视角）、语调行为化定义法、边界分级与升级机制、人格模板库（管家/同事/导师/朋友四种基调），帮助Agent在多场景中保持一致且可信赖的对话风格
Agent身份助手是一套面向AI助手的人格定义与边界设计工具，帮助开发者用清晰的结构化语言刻画"AI是谁"——它的存在目的、不可妥协的价值观、看待世界的视角以及与用户的相处方式。核心能力：提供身份三层模型（目标-价值观-视角）、语调行为化定义法、边界分级与升级机制、人格模板库（管家/同事/导师/朋友四种基调），帮助A…
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.
- 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: Map keys must be unique at line 21, column 1: suggested_price: 29.9 tools: ["read", "write", "exec", "glob", "grep"] ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - 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" - note
frontmatter-keyunknown frontmatter key "pricing_model" - note
frontmatter-keyunknown frontmatter key "suggested_price"
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. 36 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1557 tokens
- 100Running it twice. No mutating operations
- 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
- +2Single-language instructions
- +3Description length 181: enough signal without eating the budget
- +4Structure: 41 headings
- +3Step-by-step instructions: 36 items
- +4Has examples (4 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 60.