Tactic: Extract causal claims, evaluate probability of necessity (PN) and sufficiency (PS) for each, classify into necessity-sufficiency quadrants.
SkillScore77Maintained
Automatic
◆Research pack
Last verified 8/22/2026
What it changes
Passed 17 of 22 test cases with the skill, and 14 of 22 without it.
Without skill64%
With skill77%
Checks it passed that the model alone missed
Classifies the factor as INUS condition or load-bearing.
Refers to the factor as an INUS condition or load-bearing.
Identifies the overall conclusion as potentially overdetermined.
and 4 more in the full report
5 fixed12 passed either way3 still failing2 broke
Pass-rate lift
+14 pp
Tokens
+17%
Agent turns
0%
Response time
-24%
Model gemini-3.6-flashMeasured 8/22/2026v117 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 5
Prompt
A root cause analysis identifies a primary database failover script as having high necessity and high sufficiency for maintaining uptime during hardware loss. What dual terminology designates this status?
What was checked, without and with the skill
Checked
Without skill
With skill
Refers to the factor as an INUS condition or load-bearing.
Missed
Passed
case-18 · gemini-3.6-flash · 8/22/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md50 linessingle file
Causal Necessity Testing Tactic
PNS evaluation: for each causal claim, determine whether the cause is necessary, sufficient, both, or neither.
Orchestration
causal-claim-extraction extracts all X→Y causal claims from the artifact
necessity-evaluation asks: if X had NOT occurred, would Y still hold? (PN)
sufficiency-evaluation asks: if X occurred in isolation, would Y follow? (PS)