BC yi-shi-wei-jian
Use when the user says 请用/使用/调用 以史为鉴 skill, yi-shi-wei-jian, 借古鉴今, 历史类比, 中国历史案例, or 沙盘推演. Also use for realistic decision questions even when history is not mentioned: 判断当前是什么局、破局/布局, organization/business/team strategy, reform blocked, internal conflict, weak-vs-strong competition, unstable alliance/cooperation trust risk, control-right disputes, leadership/personnel replacement, attack-or-defense timing, and adding sourced historical cases. Output 【局面判断】【历史参照】【关键变量】【可选路径】【沙盘推演】【借鉴原则】【边界提醒】.
As a process C 57/100 · Has gaps — weak spots: result and completion, inputs and preconditions, progress reporting
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: 39. 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 the user says 请用/使用/调用 以史为鉴 skill, yi-shi-wei-jian, 借古鉴今,… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 57/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 100Steps. 108 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 940 tokens
- 100Running it twice. No mutating operations
- low 10 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (3 tags): a typed call is more reliable
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
- -33 of 4 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 497: enough signal without eating the budget
- +4Structure: 11 headings
- +3Step-by-step instructions: 108 items
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 70.