AC black-swan
Activate when: user says 'this can't happen,' 'never happened in N years,' 'our models say it's near-zero'; user is stress-testing a strategy or portfolio against extreme scenarios; someone mentions fat tails, Taleb, narrative fallacy, or turkey problem; a past catastrophic event is being analyzed and it 'seemed obvious in hindsight.' Do NOT activate when: the domain is genuinely thin-tailed (human heights, daily caloric intake); user is invoking 'black swan' as an excuse for a planning failure they could have avoided. More: deciqai.com/c/black-swan
Activate when: user says 'this can't happen,' 'never happened in N years,' 'our models say it's near-zero'; user is stress-testing a strategy or portfolio…
As a process C 63/100 · Has gaps — weak spots: inputs and preconditions, failures and branches, running it twice
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: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 63/100
- 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
- 30Running it twice. 1 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 60Result and completion. Output format stated, no completion criterion
- 100Tools and files. No external tools needed
- 100Steps. 25 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2162 tokens
- low 10 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
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 555: enough signal without eating the budget
- +4Structure: 16 headings
- +3Step-by-step instructions: 25 items
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 95.