BC kol-account-analysis
Use when 需要对单个达人/KOL/博主的账号做深度分析与合作评估，判断他稳定在讲什么内容、用户实际接收到了什么、商品以什么身份进入、适合什么合作形态。Triggers on: 达人分析, KOL分析, 达人账号分析, 账号深度分析, 达人研究, 博主分析, 达人合作评估, 内容母题分析, 达人内容分析, 达人投放评估, 达人风险排查. 产出可复用的账号理解与合作判断，不做批量筛选排序、投放效果预测或商品价值分析。
Use when 需要对单个达人/KOL/博主的账号做深度分析与合作评估，判断他稳定在讲什么内容、用户实际接收到了什么、商品以什么身份进入、适合什么合作形态。Triggers on: 达人分析, KOL分析, 达人账号分析, 账号深度分析, 达人研究, 博主分析, 达人合作评估, 内容母题分析, 达人内容分析…
As a process C 59/100 · Has gaps — weak spots: result and completion, inputs and preconditions, failures and branches
How to improve
- 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
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: Use when 需要对单个达人/KOL/博主的账号做深度分析与合作评估，判断他稳定在讲什么内容、用户实际接收到了什么、商品以什么身… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
Process rating: all ten parameters 59/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
- 70When it triggers. States when to use, but not when not to
- 100Tools and files. No external tools needed
- 100Steps. 17 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 705 tokens
- 100Running it twice. No mutating operations
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
- -31 of 1 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 212: enough signal without eating the budget
- +4Structure: 11 headings
- +3Step-by-step instructions: 17 items
- +4Reference files are cited in the instructions (11 of 11)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 71.