BD dispel-system
破幻·关系控制系统透视镜 + 10个角色模型。用第一性原理拆解任何一段让你困惑的关系——三层控制模型+控制惯性层、退出不等式、照妖镜/X光/清醒剂三种输出模式。包含10个配套模型：自欺型操控者、循环源代码、被征用的美德、系统协作者、控制介质、控制惯性、自断后路、误判系统、弱点雷达、内核闪光。 Dispel — Relationship Control System Lens + 10 character models. Deconstruct any confusing relationship from first principles — three control layers + control inertia layer, exit inequality, three output modes (Mirror / X-Ray / Wake-Up). Includes 10 companion models: Self-Deceiving Controller, Cycle Originator, Weaponized Virtue, System Collaborator, Control Conduit, Control Inertia, Self-Barricade, Decision Blindness, Vulnerability Radar, Inner Radiance.
破幻·关系控制系统透视镜 + 10个角色模型。用第一性原理拆解任何一段让你困惑的关系——三层控制模型+控制惯性层、退出不等式、照妖镜/X光/清醒剂三种输出模式。包含10个配套模型：自欺型操控者、循环源代码、被征用的美德、系统协作者、控制介质、控制惯性、自断后路、误判系统、弱点雷达、内核闪光。 Dispel —…
As a process D 49/100 · Unfinished process — weak spots: when it triggers, inputs and preconditions, failures and branches
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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: 12. 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") - warning
body-longSKILL.md body ≈ 11133 tokens (recommended < 5000); move details to references/ - note
frontmatter-keyunknown frontmatter key "trigger_words"
Process rating: all ten parameters 49/100
- 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
- 30Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 2 mutating operations with no state check
- 40Execution cost. Instruction body is 11133 tokens: crowds the task out of the window
- 60Tools and files. Uses tools (node) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 85Steps. 24 steps, 1 vague phrases
- 100Consistency. Name and required fields are in place
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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)
- -212 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +3Description length 606: enough signal without eating the budget
- +4Structure: 27 headings
- +3Step-by-step instructions: 24 items
- +3Output format is stated explicitly
- +4Has examples (38 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 62.