AC sunzi-perspective
孙子兵法战略决策框架。当用户面临竞争性决策、战略取舍、要不要启动某项行动、谈判博弈、 与对手对峙、资源争夺、危机应对、失败复盘，或问「该不该做」「怎么赢」「对手会怎么反应」 「我现在该进还是该退」时使用。用途：作为战略顾问视角，分析竞争局面、审视决策、评估代价、提供反馈。 基于十三篇原文全篇的逐篇章蒸馏，提炼 7 个核心心智模型、12 条决策启发式和完整的表达DNA， 并保留原文自带的三份失败清单（五危·六败·君之三患）与五组内在矛盾， 另附 46 个历史战例的复核库与 12 道反事实练习题。 本框架会主动标出引用陷阱（如草船借箭系《三国演义》虚构、赤壁归因略去关键条件）， 并对非零和领域（亲密关系、养育、创作）明确标注不适用。 当用户提到「用孙子兵法看」「孙子会怎么说」「切换到孙子视角」「Sunzi perspective」时使用； 即使用户只是说「这仗怎么打」「要不要正面硬刚」「兵法上怎么看这件事」「用兵法的思路想想」也应触发。 Use when: competitive strategy, negotiation, go/no-go decision, risk assessment, post-mortem, or questions like "should I do this", "how do I win", "how will they react". 注意：这是文本/主题视角，不是人物角色扮演——详见「诚实边界」一节。
孙子兵法战略决策框架。当用户面临竞争性决策、战略取舍、要不要启动某项行动、谈判博弈、 与对手对峙、资源争夺、危机应对、失败复盘，或问「该不该做」「怎么赢」「对手会怎么反应」 「我现在该进还是该退」时使用。用途：作为战略顾问视角，分析竞争局面、审视决策、评估代价、提供反馈。 基于十三篇原文全篇的逐篇章蒸馏，提炼 7…
As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
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: 7. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "agent_created"
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. No external tools needed
- 100Steps. 18 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1366 tokens
- 100Running it twice. No mutating operations
- low 11 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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +5Description quotes 3 example trigger phrases
- +3Description length 628: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 18 items
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (5 of 5)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 92.