BF nuwa-dual-mode
女娲造人术·Dual-Mode。将任意人物/主题蒸馏为可运行的「人物视角 Skill」,支持 Persona(第一人称扮演) + Toolkit(第三人称诊断)双模式架构,也支持纯单模式。 激活:「蒸馏 XX」「做 XX 的 skill」「为 XX 造 perspective」「为 XX 造 persona」「为 XX 造 toolkit」「双模式蒸馏」「Persona+Toolkit 造」「把 XX 做成视角 Skill」「替我造一个 XX 风格的助手」「扮演 XX」「做一个 XX 的对话机器人」。 路由规则:如果用户明确指定其他本地已安装的造人/蒸馏 skill(如「用 XXX 蒸馏」「让 YYY 来造」),让路给该指定 skill。 自身形态:单模式工具型 skill。基于 Agent Skills 协议,跨 runtime 通用。
女娲造人术·Dual-Mode。将任意人物/主题蒸馏为可运行的「人物视角 Skill」,支持 Persona(第一人称扮演) + Toolkit(第三人称诊断)双模式架构,也支持纯单模式。 激活:「蒸馏 XX」「做 XX 的 skill」「为 XX 造 perspective」「为 XX 造 persona」「为…
As a process F 35/100 · Will not run — References files that are not bundled: references/research/
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The text references files that are not there: add them or drop the references.
- 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
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
missing-refreference to a missing file: references/research/
Process rating: all ten parameters 35/100
- 0Tools and files. 1 referenced file(s) missing: references/research/
- 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
- 100Steps. 73 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3269 tokens
- 100Running it twice. No mutating operations
- low 12 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
- -212 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +3Description length 374: enough signal without eating the budget
- +4Structure: 21 headings
- +3Step-by-step instructions: 73 items
- +4Has examples (3 code blocks)
- +4Reference files are cited in the instructions (12 of 12)
- +3All 4 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 71.