BD virtual_user_skill
基于 54,000+ 条真实用研场景库的虚拟用户生成与访谈技能。通过本地向量检索匹配相关场景，生成多样化虚拟用户类型，支持深度对话访谈和产品方案测评。当用户提到虚拟用户、场景库用户、生成用户画像、用户访谈模拟、场景库检索、基于场景的用户测评时触发。注意：本技能与 virtual-user-interview（API 版）不同，本技能基于本地场景库向量检索，不依赖外部 API。
As a process D 49/100 · Unfinished process — 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 skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.
Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.
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 · 2
✓ No critical or high findings
Medium and low: 2
-
medium Dangerous commands
cmd-privilegeDEPLOYMENT.md:215Privilege escalation / world-writable permissionssudo cp virtual_user.service /etc/systemd/system/
-
low Dangerous commands
cmd-background-processDEPLOYMENT.md:216Starts a background / autostarted processsudo systemctl enable virtual_user
Files scanned: 27. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 49/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
- 40Consistency. Frontmatter name (virtual_user_skill) differs from the folder (virtual-user-skill)
- 100Tools and files. No external tools needed
- 100Steps. 23 steps
- 100Execution cost. Instruction body is 610 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
- -4Absolute local paths (C:\Users, /home/…): not portable
- -36 of 7 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 189: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 23 items
- +4Has examples (4 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 60.