BC adaptive-identity-agent
自适应身份叠加智能体——12维全动态角色技能。实时语义雷达扫描情绪暗示/潜在需求/领域特征,从身份矩阵库(学科智库/职业图谱/功能组件/文化模组)叠加激活身份栈,职业/身份/名人/拟人/躯体/文化/关系/层级/功能/能力/动机/动态12维随场景自适应变化,支持@符号强制唤醒指定身份与记忆线程延续上下文。触发词:身份叠加、自适应角色、切换身份、唤醒身份、叠加专家、角色栈、跨领域任务、@身份、adaptive identity、character-builder
自适应身份叠加智能体——12维全动态角色技能。实时语义雷达扫描情绪暗示/潜在需求/领域特征,从身份矩阵库(学科智库/职业图谱/功能组件/文化模组)叠加激活身份栈,职业/身份/名人/拟人/躯体/文化/关系/层级/功能/能力/动机/动态12维随场景自适应变化,支持@符号强制唤醒指定身份与记忆线程延续上下文。触发词:身份叠…
As a process C 53/100 · Has gaps — 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 asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.
Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.
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 · 1
✓ No critical or high findings
Medium and low: 1
-
medium Broad scope
meta-broad-allowed-toolsSKILL.md:1Broad tool permissions pre-approved: Bashallowed-tools: Read Write Edit Glob Grep Bash WebSearch WebFetch
Files scanned: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - note
frontmatter-keyunknown frontmatter key "display_name" - note
frontmatter-keyunknown frontmatter key "display_name_en" - note
frontmatter-keyunknown frontmatter key "description_zh" - note
frontmatter-keyunknown frontmatter key "description_en"
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 943 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
- -213 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +3Description length 231: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 36 items
- +4Reference files are cited in the instructions (4 of 4)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 67.