BC framework-analysis
基于钱学森"框架法"的系统科学分析工具。用于对地缘政治冲突、国际危机、历史事件等复杂系统进行结构化终局推导。 核心方法论来自钱学森《用系统科学方法使历史科学定量化》： 1. 建立结构性约束框架（不是列出因素，而是找到不会变的硬条件） 2. 填入经过验证的事实 3. 通过因果链推导唯一结论（不做情景列举，不做概率分布） 4. 给出可证伪预测 当用户提到：框架法分析、终局推导、钱学森方法论、系统科学分析地缘事件、结构性约束分析时使用此 skill。 不在用户仅提到"分析一下XX"等模糊请求时激活（可能只需要普通搜索或调研）。
As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
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 · 0
✓ No critical or high findings
Files scanned: 2. 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")
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. 25 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 633 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
- +1No license
- +2Single-language instructions
- +3Description length 263: enough signal without eating the budget
- +4Structure: 15 headings
- +3Step-by-step instructions: 25 items
- +4Has examples (5 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.